{{tag>Brouillon podman}} # Notes podman machine ~~~bash podman machine init vm1 podman machine start vm1 podman machine status vm1 ~~~ ~~~bash podman machine stop vm1 ~~~ ~~~ $ podman machine rm vm1 The following files will be deleted: /home/jibe/.config/containers/podman/machine/qemu/vm1.json /run/user/1000/podman/vm1.sock /run/user/1000/podman/vm1-gvproxy.sock /run/user/1000/podman/vm1-api.sock /run/user/1000/podman/vm1.log /run/user/1000/podman/vm1_vm.pid /run/user/1000/podman/qmp_vm1.sock Are you sure you want to continue? [y/N] y ~~~ ## Pb ### Err - could not find "gvproxy" ~~~ $ podman machine start vm1 Starting machine "vm1" Error: could not find "gvproxy" in one of [/usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman]. To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries. ~~~ #### Solution ~~~bash sudo apt-get install gvproxy sudo ln -s $(which gvproxy) /usr/libexec/podman/ ~~~ ### Err - "virtiofsd": executable file not found in $PATH ~~~ $ podman machine start vm1 Starting machine "vm1" ERRO[0000] process 28237 has not ended Error: failed to find virtiofsd: exec: "virtiofsd": executable file not found in $PATH ~~~ #### Solution ~~~bash sudo apt-get install virtiofsd export PATH=$PATH:/usr/libexec/ ~~~ ~~~ $ podman machine start vm1 Starting machine "vm1" This machine is currently configured in rootless mode. If your containers require root permissions (e.g. ports < 1024), or if you run into compatibility issues with non-podman clients, you can switch using the following command: podman machine set --rootful vm1 Mounting volume... /home/jibe:/home/jibe API forwarding listening on: /run/user/1000/podman/vm1-api.sock You can connect Docker API clients by setting DOCKER_HOST using the following command in your terminal session: export DOCKER_HOST='unix:///run/user/1000/podman/vm1-api.sock' Machine "vm1" started successfully ~~~ FIXME