- Podman - Podman List Archives

podman on rhel8 version 1.0.3 why so old ?
by nikolaj＠majorov.biz 07 Aug '19

07 Aug '19

Hi, just installed fresh rhel8 and install podman . [vagrant@rhel8 ~]$ sudo podman version Version: 1.0.3 Go Version: go1.11.5 OS/Arch: linux/amd64 why podman here is so old ? [vagrant@rhel8 ~]$ sudo subscription-manager list +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux for x86_64 Product ID: 479 Version: 8.0 Arch: x86_64 Status: Subscribed Status Details: Starts: 02/21/13 Ends: 12/31/21

2 1

container running in pod don't get ip address
by nikolaj＠majorov.biz 06 Aug '19

06 Aug '19

Hi I running container in pod and it is not getting an ip address. sudo podman pod create --name drupal -p 3306 -p 8080:80 -p 8443:443 sudo podman run --pod drupal \ -e MARIADB_USER=bn_drupal \ -e MARIADB_PASSWORD=drupal \ -e MARIADB_ROOT_PASSWORD=redhat \ -e MARIADB_DATABASE=bitnami_drupal \ --volume mariadb_data:/bitnami \ --rm -it docker.io/bitnami/mariadb:10.3 so then I inspect network setting of container in the pod it is not getting an ip address: podman inspect --format "{{.NetworkSettings}}" 05905843e7d6 { false 0 [] [] [] 0 0 } if I run same container without a pod I get an ip address: sudo podman run -e MARIADB_USER=bn_drupal \ -e MARIADB_PASSWORD=drupal \ -e MARIADB_ROOT_PASSWORD=redhat \ -e MARIADB_DATABASE=bitnami_drupal \ --volume mariadb_data:/bitnami \ --rm -it docker.io/bitnami/mariadb:10.3 podman inspect --format "{{.NetworkSettings}}" 3f760c0aad51 { false 0 [] /var/run/netns/cni-b8f71228-9609-8585-5952-4112548c737b [] [] 10.88.0.1 0 10.88.0.7 16 92:62:fd:37:1b:bb} why it happens ? is there something I forget or missing ? [vagrant@localhost ~]$ podman version Version: 1.4.4 RemoteAPI Version: 1 Go Version: go1.12.7 OS/Arch: linux/amd64

4 5

Can't connect container by name
by Uwe Reh 02 Aug '19

02 Aug '19

Hi, I'm trying to migrate a small set of containers from Docker to Podman. Obviously I missed one or two links, because I can't get the ensemble run, like I'm used to. *Problem: Having two containers, C1 and C2. Running on Docker, the containers can establish bridged IP4 connections on each other byIp and byName. With podman it works fine with IP's (found with podman inspect) but I wasn't able to resolve any name. > podman exec -it C1 ping 10.88.0.7 > PING 10.88.0.7 (10.88.0.7): 56 data bytes > 64 bytes from 10.88.0.7: seq=0 ttl=64 time=0.105 ms > podman exec -it C1 ping C2 > ping: bad address 'C2' *Question: What have I missed to have dynamic DNS service for the containers inside the bridge or slirp4netns? *Runtime: > podman version > Version: 1.4.4 > RemoteAPI Version: 1 > Go Version: go1.12.6 > OS/Arch: linux/amd64 on > cat /etc/os-release > NAME="openSUSE Leap" > VERSION="15.0" > ID="opensuse-leap" Uwe

2 2

Query on how to use python-podman as root
by Jayjeet Chakraborty 01 Aug '19

01 Aug '19

Hello Podman Community, I was trying to use python-podman as non-root when I was facing the issue https://github.com/containers/python-podman/issues/16. I would like to know if there is any way to bypass this issue by running podman as root through python-podman. Any help would be appreciated. Thank you. JayjeetChakraborty https://github.com/JayjeetAtGithub

3 2

Problems with Podman in systemd
by Eric Gustavsson 11 Jul '19

11 Jul '19

Hi all, I've been having issues with systemd and Podman. Especially when the service is restarting. Starting it initially works without problem, though when restarting I run into one of two issues. --reboot-- Jul 08 10:00:49 KeyraGuest1 systemd[1]: Started Bitwarden. Jul 08 10:00:59 KeyraGuest1 podman[536]: Error: could not get runtime: error creating tmpdir /run/user/1000/libpod/tmp: mkdir /run/user/1000: permission denied Jul 08 10:00:59 KeyraGuest1 systemd[1]: bitwarden.service: Main process exited, code=exited, status=125/n/a Jul 08 10:00:59 KeyraGuest1 systemd[1]: bitwarden.service: Failed with result 'exit-code'. Jul 08 10:01:29 KeyraGuest1 systemd[1]: bitwarden.service: Service RestartSec=30s expired, scheduling restart. Jul 08 10:01:29 KeyraGuest1 systemd[1]: bitwarden.service: Scheduled restart job, restart counter is at 1. Jul 08 10:01:29 KeyraGuest1 systemd[1]: Stopped Bitwarden. And: Jul 08 10:01:29 KeyraGuest1 systemd[1]: Started Bitwarden. Jul 08 10:01:39 KeyraGuest1 podman[914]: 2019-07-08 10:01:39.067436802 +0000 UTC m=+1.076662432 system refresh Jul 08 10:01:53 KeyraGuest1 podman[894]: Error: error creating container storage: the container name "bitwarden" is already in use by "34fb34844382c9118be3d377e9f41de6f21485329c824cdd0da109304a2506f3". You have to remove that container to be able to reuse that name.: that name is already in use Jul 08 10:01:53 KeyraGuest1 systemd[1]: bitwarden.service: Main process exited, code=exited, status=125/n/a Jul 08 10:01:53 KeyraGuest1 systemd[1]: bitwarden.service: Failed with result 'exit-code'. Jul 08 10:02:23 KeyraGuest1 systemd[1]: bitwarden.service: Service RestartSec=30s expired, scheduling restart. Jul 08 10:02:23 KeyraGuest1 systemd[1]: bitwarden.service: Scheduled restart job, restart counter is at 2. Jul 08 10:02:23 KeyraGuest1 systemd[1]: Stopped Bitwarden. I've attached the bitwarden_service, which runs podman with --rm, so it should automatically remove the pod from before. With the first issue with permission denied, I'm not sure what's causing that either. Any help would be appreciated :) Thanks, Eric Gustavsson He / Him Associate Software Engineer Red Hat <https://www.redhat.com> IM: Telegram: @SpyTec <https://www.redhat.com>

2 4

SELinux denials on pod member containers for hosts and resolv.conf
by Chris Vale 09 Jul '19

09 Jul '19

Hello, Just starting to experiment with Podman on RHEL8 and I’m seeing SELinux denials (on the host) related to containers I create within a pod for the files automatically created as overlays, most typically hosts and resolv.conf, when performing network related tasks that require name resolution. Of course the containers are unable to read the files in question due to the denials. I don’t see this behavior when deploying containers outside of a pod. On containers that work as expected I notice the SELinux type for the files in question on the host are container_file_t. However, for containers that experience the denials the SELinux type for the files in question on the host are set to container_var_run_t. Interestingly enough the pod infrastructure container has files labeled with container_file_t Is this normal behavior for containers added to a pod or perhaps I’m missing something?

3 3

CMD file not found
by Boyd Kelly 04 Jul '19

04 Jul '19

Hi, I'm just exploring podman and buildah, but noticed something weird; not sure if it could be a bug or misconfiguration. But I don't know where to look for clues as to what is happening. Sometimes when I start a container I get a file not found error message and then 2 seconds later it starts and runs just fine. What could be the problem? Thanks for any suggestions. (This is a container running Fedora 30) [bkelly@zbox ~]$ podman container start syncthing Error: unable to start container "syncthing": time="2019-07-04T07:23:41Z" level=error msg="container_linux.go:346: starting container process caused \"exec: \\\"/startup.sh\\\": stat /startup.sh: no such file or directory\"\n" container_linux.go:346: starting container process caused "exec: \"/startup.sh\": stat /startup.sh: no such file or directory" : OCI runtime error [bkelly@zbox ~]$ podman container start syncthing syncthing

3 3

Setting up 2 containers
by Christoffer Reijer 29 Jun '19

29 Jun '19

This seems like a pretty basic use case but I cannot seem to find out how to do this: I want to create two containers, foo and bar, and have them talk to each other on ports that are not exposed to anything else. I used to do this by creating a docker network, my_network, that I attached my two containers to, and then I could access foo.my_network from the bar container. But how moving to RHEL 8 I have to port my code away from Docker and I can't figure out how to get my two containers to talk. It works fine on IP (10.88.0.10 and 10.88.0.11) but I would prefer to use the name since I don't trust the IP to be the same at every run. Any ideas?

6 14

Including file system changes in container migration
by Adrian Reber 25 Jun '19

25 Jun '19

The current container migration implementation in Podman cannot handle changes to the file-system. If a container changes a file the recommendation is to mount that directory as a tmpfs and then the changed file will be correctly migrated to the destination system. If something changes a file in /tmp for example, following steps are currently necessary: # podman run -d --tmpfs /tmp <container> # podman container checkpoint -l -e /tmp/chkpt.tar.gz # scp /tmp/chkpt.tar.gz destination-host:/tmp On the destination host of the migration: # podman container restore -i /tmp/chkpt.tar.gz Files changed in /tmp in the container will also be in the restored container on the destination host, because CRIU automatically handles tmpfs directories. To make it easier for users to not have to mark all changed directories as --tmpfs I would like to include changed files in the checkpoint archive (/tmp/chkpt.tar.gz from my example). One possible implementation could use vendor/github.com/containers/storage/store.go: // Diff returns the tarstream which would specify the changes returned // by Changes. If options are passed in, they can override default // behaviors. Diff(from, to string, options *DiffOptions) (io.ReadCloser, error) This sounds exactly like what I need. I get a tarstream which I can embed into the checkpoint archive and which can then be used with ApplyDiff() before restoring the container. Does this sound like the right approach to also migrate file-system changes during container migration? Adrian

3 4

Inter-container communication in pod
by Dominik Matis 19 Jun '19

19 Jun '19

Hi, I have a situation in which I have React app in container, which is exposed to port 3000 to be able to access it from host and I also have another container for Express API server, which is listening on port 8000, but I don't want it to be accessible from host. Is it somehow possible to run these two containers simultaneously in one pod and have exposed only port 3000, so we can see the page? Thanks for a reply. Best regards, Dominik Matis

2 1