Podman is getting increasingly powerful in managing containers, pods, and images. Seamlessly work with containers and Kubernetes from your local environment.
In some cases, you need to configure your Podman machine. This blog post is an example of using information from the Podman documentation to configure your machine. ()
The next step shows the everyday tasks to adjust Podman to your needs.
Note: Easy was to install Podman is using the Podman Desktop.
- When you delete a machine, be aware that the related Podman volumes and configurations you did before will also be deleted by this command.
podman machine stop
podman machine rm
- In the command below, we create an example configuration. Here, we set the machine to rootful and change the CPU, memory disk size with a starting point.
podman machine init \
--rootful \
--cpus 4 \
--memory 8048 \
--disk-size 150 \
--now --disk-size 100
- The terminal output
Looking up Podman Machine image at quay.io/podman/machine-os:5.2 to create VM
Extracting compressed file: podman-machine-default-arm64.raw: done
Machine init complete
Starting machine "podman-machine-default"
API forwarding listening on: /var/run/docker.sock
Docker API clients default to this address. You do not need to set DOCKER_HOST.
Machine "podman-machine-default" started successfully
- If you want to change the configuration without deleting you existing machine you can use the podman machine set command.
Example commands:
podman machine stop
podman machine set --memory 8048
podman machine set --rootful
podman machine start
That’s all!
Note: Maybe your MacOS terminal doesn’t show the ‘podman’ command, but you have installed it.
- Verify which shell is used:
ps -p $$
PID TTY TIME CMD
15165 ttys010 0:00.14 /bin/zsh -il
Add the command into the terminal configuration /bin/zsh -il at the startup.
I hope this was useful to you and let’s see what’s next?
Greetings,
Thomas
#podman, #container, #configuration
Thomas Suedbroecker's Blog 