docker and podman.init: 20240224)docker and podman.
We note that NVIDIA’s Container Toolkit officially only supports Ubuntu LTS release.nvidia-driver.Software & Updates’s Additional Drivers and reboot.ubuntu-drivers devices and install the recommended “server” driver: sudo apt install nvidia-driver-535-server, then reboot.aplay error, you can sudo apt-get install alsa-utilsnvidia-smi from a terminal; if a valid prompt shows up, you will have information on the Driver Version and the supported CUDA Version for future running GPU-enabled containers.nvidia-smi tells me 535 supports up to CUDA 12.2, which requires me to use a more recent version of the driver. You can find the list of Nvidia drivers from https://www.nvidia.com/en-us/drivers/unix/sudo ubuntu-drivers list offers driver 550 in the provided list, you can perform a sudo ubuntu-drivers install nvidia:550 and ignore the rest of this section.apt list --installed | grep nvidia | grep modules
linux-modules-nvidia-535-generic-hwe-24.04 matches the expected linux-modules-nvidia-${DRIVER_BRANCH}${SERVER}-${LINUX_FLAVOUR} format.apt search nvidia | grep 550 | grep modules | grep generic-hwe
server, for example) is linux-modules-nvidia-550-generic-hwe-24.04, which we will install:sudo apt install linux-modules-nvidia-550-generic-hwe-24.04
sudo apt-cache policy linux-modules-nvidia-550-$(uname -r)
Installed and Candidate versions should match. You can also test reinstallation using sudo apt install linux-modules-nvidia-550-$(uname -r)sudo apt install nvidia-driver-550
nvidia-smi which in this case now returns:+-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.90.07 Driver Version: 550.90.07 CUDA Version: 12.4 | |-----------------------------------------+------------------------+----------------------+
sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update
Using NVIDIA driver metapackage From nvidia-driver-560 (proprietary)) and start the installation process. After the installation is completed, a reboot is required. At next login, we can confirm the driver and its capabilities using nvidia-smi:+-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 560.35.03 Driver Version: 560.35.03 CUDA Version: 12.6 | |-----------------------------------------+------------------------+----------------------+
apt registry option.
Details can be found at https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository.for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg; done
# Add Docker's official GPG key: sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc # Add the repository to Apt sources: echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
docker is functional by checking if we get the Hello from Docker! message running its hello-world:sudo docker run --rm hello-world
docker available without sudo, which has some security implications, as detailed in https://docs.docker.com/engine/install/linux-postinstall/. docker run hello-world without the need for a sudo:sudo usermod -aG docker $USER
apt search podman returns versions above 4.1.0, the minimum required to use the Container Device Interface (CDI) for nvidia-container-toolkit.podman by simplysudo apt install podman
podman:podman run hello-world
podman runs similarly to docker; for example:podman run --rm -it docker.io/ubuntu:24.04 /bin/bash
ubuntu:24.04, give you a bash shell prompt in an interactive session, and will delete the created container when you exit the shell.docker.io/ubuntu:24.04.docker.io to the list of “unqualified search registries,” edit/etc/containers/registries.conf and modify the following line as follows: unqualified-search-registries=["docker.io"]—more details on that topic at https://podman.io/docs/installation#registriesconf.docker, podman does not create iptables configurations or use br_netfilter, which allows for the use of bridged VMs. In such cases, only install podman and also install podman-compose to get access to podman-compose. Usepodman-compose if you want to use a tool like Dockge; but we also recommend seeing this PR.podman.curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \ && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \ sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \ sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
sudo apt-get update sudo apt-get install -y nvidia-container-toolkit
docker to recognize the toolkit:sudo nvidia-ctk runtime configure --runtime=docker
dockersudo systemctl restart docker
docker (no sudo needed if you made the optional step in the last section) sees any GPU that you have running on your system by having it run nvidia-smi. Note that docker will need both --runtime=nvidia and --gpus all to use the proper runtime and have access to all the GPUsdocker run --rm --runtime=nvidia --gpus all nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi
CUDA version returned by the nvidia-smi command on your host (without docker) will inform you of the max cuda:version image that you can use./etc/docker/daemon.json file to see that the nvidia-container-runtime is added:[...] "runtimes": { "nvidia": { "args": [], "path": "nvidia-container-runtime" } }
"default-runtime": "nvidia", (after the first {) and sudo systemctl restart docker. You should not have to add --runtime=nvidia to the CLI anymore.podman we will base the instructions for Container Device Interface (CDI) setup on https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/cdi-support.html.nvidia-ctk --version
NVIDIA Container Toolkit CLI version 1.15.0 sudo nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
INFO[0001] Generated CDI spec with version 0.5.00, GPU-ID and all)grep " name:" /etc/cdi/nvidia.yaml
podman (no sudo needed) using the proper devices --device nvidia.com/gpu=allpodman run --rm --device nvidia.com/gpu=all ubuntu nvidia-smi
podman only on hosts where you intend to use bridged VMs.
Linux host set-up instructions for Dockge, a self-hosted Docker Compose stacks management tool with a feature-rich interface for self-hosting and home lab setups. It provides access to an all-in-one view of logs, a YAML editor, a web terminal, container controls, and monitoring.
This guide details how to install quickemu on a Linux Ubuntu 24.04 server to run desktop VMs (here, we will install Ubuntu 24.04 Desktop) on the same subnet IP range as the host's primary subnet using a network bridge. Those VMs are remotely accessible on the subnet using a SPICE client. This setup will provide VMs directly accessible on the subnet where the Linux server is running. Because we will specify the MAC addresses of those VMs, we can apply reserved DHCP IPs from our router and allow adding and configuring extra services within hardware firewalls, such as the Firewalla (for example, DNS-over-HTTPS).
Docker has become a cornerstone of the modern development stack: how applications are built, shipped, and run. It is an excellent solution to the portability problem: containers run consistently on any machine, eliminating the "it works on my machine" problem. It leverages containers: self-contained units of software that package the components needed for an application to run. This primer introduces its core concepts.