140 lines
5.6 KiB
Markdown
140 lines
5.6 KiB
Markdown
# Multus CNI packaged by Bitnami
|
|
|
|
## What is Multus CNI?
|
|
|
|
> Multus is a CNI plugin for Kubernetes clusters. Written in Go, features adding multiple network interfaces to pods.
|
|
|
|
[Overview of Multus CNI](https://github.com/k8snetworkplumbingwg/multus-cni)
|
|
|
|
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
|
|
|
|
## TL;DR
|
|
|
|
```console
|
|
docker run -it --name multus-cni bitnami/multus-cni
|
|
```
|
|
|
|
### Docker Compose
|
|
|
|
```console
|
|
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/multus-cni/docker-compose.yml > docker-compose.yml
|
|
docker-compose up -d
|
|
```
|
|
|
|
## Why use Bitnami Images?
|
|
|
|
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
|
|
* With Bitnami images the latest bug fixes and features are available as soon as possible.
|
|
* Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
|
|
* All our images are based on [minideb](https://github.com/bitnami/minideb) a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
|
|
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
|
|
* Bitnami container images are released on a regular basis with the latest distribution packages available.
|
|
|
|
Looking to use Multus CNI in production? Try [VMware Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
|
|
|
|
## Supported tags and respective `Dockerfile` links
|
|
|
|
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
|
|
|
You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`.
|
|
|
|
Subscribe to project updates by watching the [bitnami/containers GitHub repo](https://github.com/bitnami/containers).
|
|
|
|
## Get this image
|
|
|
|
The recommended way to get the Bitnami Multus CNI Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/multus-cni).
|
|
|
|
```console
|
|
docker pull bitnami/multus-cni:latest
|
|
```
|
|
|
|
To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/multus-cni/tags/) in the Docker Hub Registry.
|
|
|
|
```console
|
|
docker pull bitnami/multus-cni:[TAG]
|
|
```
|
|
|
|
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.
|
|
|
|
```console
|
|
git clone https://github.com/bitnami/containers.git
|
|
cd bitnami/APP/VERSION/OPERATING-SYSTEM
|
|
docker build -t bitnami/APP:latest .
|
|
```
|
|
|
|
## Maintenance
|
|
|
|
### Upgrade this image
|
|
|
|
Bitnami provides up-to-date versions of Multus CNI, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
|
|
|
|
#### Step 1: Get the updated image
|
|
|
|
```console
|
|
docker pull bitnami/multus-cni:latest
|
|
```
|
|
|
|
or if you're using Docker Compose, update the value of the image property to `bitnami/multus-cni:latest`.
|
|
|
|
#### Step 2: Remove the currently running container
|
|
|
|
```console
|
|
docker rm -v multus-cni
|
|
```
|
|
|
|
or using Docker Compose:
|
|
|
|
```console
|
|
docker-compose rm -v multus-cni
|
|
```
|
|
|
|
#### Step 3: Run the new image
|
|
|
|
Re-create your container from the new image.
|
|
|
|
```console
|
|
docker run --name multus-cni bitnami/multus-cni:latest
|
|
```
|
|
|
|
or using Docker Compose:
|
|
|
|
```console
|
|
docker-compose up multus-cni
|
|
```
|
|
|
|
## Configuration
|
|
|
|
### Running commands
|
|
|
|
To run commands inside this container you can use `docker run`, for example to execute `multus-daemon --help` you can follow the example below:
|
|
|
|
```console
|
|
docker run --rm --entrypoint /opt/bitnami/multus-cni/bin/multus-daemon --name multus-cni bitnami/multus-cni:latest --help
|
|
```
|
|
|
|
Check the [official Multus CNI documentation](https://github.com/k8snetworkplumbingwg/multus-cni) for more information about how to use Multus CNI.
|
|
|
|
## Contributing
|
|
|
|
We'd love for you to contribute to this Docker image. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.
|
|
|
|
## Issues
|
|
|
|
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/containers/issues/new/choose). For us to provide better support, be sure to fill the issue template.
|
|
|
|
## License
|
|
|
|
Copyright © 2023 VMware, Inc.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
<http://www.apache.org/licenses/LICENSE-2.0>
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|