- Podman - Podman List Archives

podman upgrade from 1.4 to 1.7 on Redhat 7.7
by José Osorio R. 01 Feb '20

01 Feb '20

Hello All, I'm struggling to upgrade the podman version I installed in Redhat 7.7, whici is 1.4. Is there a way to upgrade it? I can not find the latest rpm for redhat. Thanks Regards Jose Osorio

1 0

oddities re: explanations for libpod.conf, mounts.conf, storage.conf
by Robert P. J. Day 31 Jan '20

31 Jan '20

was trying to summarize the possibilities for config files: - mounts.conf - storage.conf - libpod.conf and ended up falling into a maze of twisty passages, all alike. (all this is based on packaged podman-1.7.0 on fedora 31). first, from "man podman", those three files are explained thusly: libpod.conf (/usr/share/containers/libpod.conf) libpod.conf is the configuration file for all tools using libpod to manage containers, when run as root. Administrators can override the defaults file by creating `/etc/containers/libpod.conf`. When Podman runs in rootless mode, the file `$HOME/.config/containers/libpod.conf` is created and replaces some fields in the system configuration file. mounts.conf (/usr/share/containers/mounts.conf) The mounts.conf file specifies volume mount directories that are automatically mounted inside containers when executing the `podman run` or `podman start` commands. Administrators can override the defaults file by creating `/etc/containers/mounts.conf`. When Podman runs in rootless mode, the file $HOME/.config/con‐ tainers/mounts.conf will override the default if it exists. Please refer to containers-mounts.conf(5) for further details. storage.conf (/etc/containers/storage.conf) storage.conf is the storage configuration file for all tools using containers/storage When Podman runs in rootless mode, the file `$HOME/.config/containers/storage.conf` is used instead of the system defaults. so the first inconsistency(?) is that the first two files have a possibly default version under /usr/share/containers, while storage.conf does not -- according to "man podman", the default file will be in /etc/containers. it's not clear why the inconsistency. the next oddity is that the first two files are contributed by two different fedora packages: $ rpm -qf /usr/share/containers/libpod.conf podman-1.7.0-2.fc31.x86_64 $ rpm -qf /usr/share/containers/mounts.conf containers-common-0.1.40-4.fc31.x86_64 that may not sound like a big deal but it does allow for some inconsistency in how those two packages either supply or explain things, which is what you see when you "man containers-storage.conf": Distributions often provide a /usr/share/containers/stor‐ age.conf file to define default storage configuration. Adminis‐ trators can override this file by creating /etc/contain‐ ers/storage.conf to specify their own configuration. The stor‐ age.conf file for rootless users is stored in the $HOME/.con‐ fig/containers/storage.conf file. so "man podman" does *not* mention the possibility of /usr/share/containers/storage.conf, while "man containers-storage.conf" *does*. finally, i thought, "oh, just RTFS" to see what is really happening, and in libpod/config/config.go (amd i am *not* a go expert), it seems like libpod.conf is supported being under /usr/share/containers, but i don't see where the other two files (mounts.conf, storage.conf) are similarly supported, although i could be just misreading badly. i'm just trying to clarify the configuration file possibilities. rday

2 1

pathless execution of iptables
by Julen Landa Alustiza 31 Jan '20

31 Jan '20

Good morning everyone I'm using duply on my homelab backup system and noticed today that when I include a podman run blablabla on a pre script, this is trying to call 'iptables' without any path, and results that duply does not add /usr/sbin to the $PATH on the pre scripts execution environment when is executed as root, so the iptables call ends with an error: Output: time="2020-01-23T02:00:02+01:00" level=error msg="Error adding network: failed to locate iptables: exec: \"iptables\": executable file not found in $PATH" time="2020-01-23T02:00:02+01:00" level=error msg="Error while adding pod to CNI network \"podman\": failed to locate iptables: exec: \"iptables\": executable file not found in $PATH" Error: error configuring network namespace for container fbaad57e6a9d1894624b67cb2f3e9d8483af56bf71680befabfbb85fd589e640: failed to locate iptables: exec: "iptables": executable file not found in $PATH So I'm asking here... should we rely on $PATH to reach iptables executable, or hardcode /usr/sbin as it path? If an attacker managed to alter my $PATH, could open an attack vector due to this $PATH thing and use a malicious iptables located on a different path with higher precedence on my $PATH ? Regards,

4 5

Strange password behavior with mysql container
by Sebastiaan 31 Jan '20

31 Jan '20

Hi there, I'm fairly new to Podman so apologies if my question seems simple, but seem to be experiencing some odd behavior with Mysql and no amount of googling has yielded answers. I'm using Podman 1.70 on Fedora 31. If i create a container using the following command: podman run -dt --name mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=<password> mysql it creates a running container without a problem. If i perform an inspection I can also see that the MYSQL_ROOT_PASSWORD environment variable is set correctly. Logging into the container is another story. If I try to do: podman exec -it mysql mysql -u root -p I get a login prompt, but entering my password results in ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) Error: non zero exit code: 1: OCI runtime error However, if I do: podman exec -it mysql bash and get into a bash prompt inside the container, and then do: mysql -u root -p ( i.e. effectively the exact same command ) I am able to login with the exact same password. It seems when I try to use podman exec to go straight to the mysql commandline, it is garbling or mangling my password. Could it be something locale or charmap related? Or is it a bug? Same issue if I try to connect using PHPMyadmin, adminer, wordpress etc - it just won't let me login using my password ( which I know does work ). Any tips on how I could get this to work? Surely people have successfully managed to get mysql working with podman? Kind Regards Sebastiaan Stoffels

3 3

systemd example for pods?
by Brian Fallik 30 Jan '20

30 Jan '20

Hi, Does anyone have an example they can share of managing a pod in systemd? I'm trying to follow the guidelines outlined in https://www.redhat.com/sysadmin/podman-shareable-systemd-services which work great for containers but now I'm unsure how to proceed for a pod. Ultimately I'm trying to deploy prometheus alongside nginx as a reverse proxy, and deploying both containers inside a pod seems easiest from a networking perspective and also sensible logic since the two containers are coupled into a single, functional unit. For the case of the pod, what PID does systemd track? Is it the pause container? If so, how does that happen? `podman pod create` doesn't seem to accept --conmon-pidfile args like `podman run` does. I also tried using the output of `podman generate systemd` but that seems tied to a specific pod instance. Ideally I'd find something more generic like the pattern I extracted from the blog post above. Thanks in advance, brian

2 2

Release 1.7.1
by alexander.v.litvak＠gmail.com 29 Jan '20

29 Jan '20

Is there a chance 1.7.1 will be released any time soon?

2 2

Cannot set startup script when saving image - very confused
by Dev Linux 29 Jan '20

29 Jan '20

I have a running container, and I wish to save it as an image, specifying a startup script (bash script) when it is launched. Inside the container, before saving to image, I have created a file: /home/data/bin/run.sh The first line in /home/data/bin/run.sh is: #!/bin/bash *I save the image with this command:* *$podman commit --change "CMD=/home/data/bin/run.sh" <container_id> <img_name>* Then I try to run the image, instantiating a container, and I get an error: */bin/sh: /bin/sh: cannot execute binary file* I don't understand why it is using */bin/sh*. At the very top of my *run.sh I have: #!/bin/bash* --- I tried something slightly different, saving the image using the following command, and I get the same error message: *$podman commit --change "CMD=/bin/bash /home/data/bin/run.sh" $ID $NAME* Any ideas would be greatly appreciated, thank you.

2 1

Creating an image from a container issue with <none> images created.
by Dev Linux 29 Jan '20

29 Jan '20

If I have a running container, and get the ID by issuing this command: $podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc41dd5034b8 registry.redhat.io/ubi8:latest /bin/bash 25 hours ago Up About an hour ago tender_curran --- And then create an image from that container, giving it the same name of an already existing image ($podman <id_of_container> <name_of_image>: $podman commit bc41dd5034b8 ubi8-template It appears that the previously existing image, with the same name is kept, with an entry like so: $podman images <none> <none> b3cb81594745 About an hour ago 1.35 GB --- Is it OK to delete this <none> image? or is it attached in any way to the container that replaced it? --- Why is it created? I simply want to overwrite destructively the image with the same name. Is there a command line switch that will prevent these <none> images?

2 1

couple questions about "podman pause"
by Robert P. J. Day 29 Jan '20

29 Jan '20

first, what is the difference between "podman pause" and "podman stop", particularly since "man podman-pause" seems to confuse the two: OPTIONS --all, -a Pause all running containers. EXAMPLE ... snip ... Pause all running containers. podman stop -a ^^^^ so anyone reading "man podman-pause" is going to think that "stop" is a synonym, at least reading that example. in addition, "man podman-stop" doesn't help the situation by not distinguishing between paused and stopped containers: OPTIONS --all, -a Stop all running containers. This does not include paused con‐ tainers. second issue: $ podman pause musing_knuth Error: pause is not supported for rootless containers $ even if this is true, there is nothing in "man podman-pause" to suggest that this might occur, which is definitely grounds for confusion. rday

3 4

crun vs systemd and /run/user/0/crun
by Sage Weil 29 Jan '20

29 Jan '20

Hi, On my fedora 31 box, podman + crun are putting state in /run/user/0/crun. This is fine until I ssh into the box as root and then log out, at which point systemd blows away all of /run/user/0, and podman half-breaks (can't podman exec, podman kill on containers fails to stop conmon, etc.). I'm not sure why it's using /run/user/0/crun instead of /run/crun, though, since I'm starting the containers as UID 0. It looks like the conmon process as the XDG_RUNTIME_DIR=/run/user/0 set in its environment. Why does libpod set that, though, when the user is root? Using /run/user/0 seems like a fundamentally broken strategy, since that is an ephemeral directory that systemd will blow away when the user logs out... FWIW I'm running podman-1.6.2-2.fc31.x86_64 crun-0.10.6-1.fc31.x86_64 Thanks! sage

2 1