February 2020 - Podman - Podman List Archives

shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day 13 Dec '24

13 Dec '24

"man podman-build" suggests that the context argument is optional: SYNOPSIS podman build [options] [context] podman image build [options] [context] ... If no context directory is specified, then Podman will assume the current working directory as the build context, which should contain the Containerfile. but if i have a directory with nothing but a Containerfile, i get: $ podman build Error: no context directory specified, and no containerfile specified $ OTOH, specifying context of current directory: $ podman build . STEP 1: FROM alpine:latest ... etc etc ... thoughts? rday

4 5

Problem restarting a mysql container
by Simon Colston 17 Mar '20

17 Mar '20

I'm running podman version 1.8.0 on Fedora 31 If I run with this command podman run --userns=keep-id \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0 I can connect with the mysql client with no errors. mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. etc. If I then do: podman stop mysql podman start mysql then I can no longer connect with the mysql client. mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111) I then reset everything: podman stop mysql podman rm mysql and delete all the database files. If I remove the --userns=keep-id argument I can connect after a 'stop' and a 'start'. (Except that the database files now have an odd user id that I can only delete as root) So, --userns=keep-id is the only difference and causing some sort of problem after a restart. I had this working using podman version 1.7 and I think that (and maybe the kernel) are the only things that have changed. Am I doing something wrong? Have I found a bug and would you like me to submit it? Simon

2 2

Podman for MacOS - Valid Approach ?
by Ezequiel Aguilar 22 Feb '20

22 Feb '20

Hello Guys, Is this a valid approach for running Podman in MacOS ? https://developers.redhat.com/blog/2020/02/12/podman-for-macos-sort-of/ It seems similar to Docker Machine, and it works well for me. Any thoughts? Regards, Ezequiel

4 6

max open files
by bryan.hepworth＠gmail.com 20 Feb '20

20 Feb '20

Hi all Some of my users have bumped up against max open files when trying to commit a container image with podman. Does anyone know where this is set in rhel 8.1? Thanks Bryan

3 4

httpd install failure
by Seth Kenlon 20 Feb '20

20 Feb '20

Since Fedora 31, I can't seem to get a web server to install successfully into an image. I get failure with Nginx and Apache, and it "feels" like the failure is probably a post-install action because the RPM gets installed by dnf, it just ends in failure: ``` $ buildah run centos-working-container-6 dnf install nginx -y Installed: [...] nginx-all-modules-1:1.14.1-9.module_el8.0.0+184+e34fea82.noarch nginx-filesystem-1:1.14.1-9.module_el8.0.0+184+e34fea82.noarch nginx-mod-http-image-filter-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 nginx-mod-http-perl-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 nginx-mod-http-xslt-filter-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 nginx-mod-mail-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 nginx-mod-stream-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 [...] Failed: nginx-1:1.14.1-9.module_el8.0.0+184+e34fea82.x86_64 Error: Transaction failed ``` Installing pretty much anything else works: ``` $ buildah run centos-working-container-6 dnf install lua -y [...] Installed: lua-5.3.4-11.el8.x86_64 Complete! ``` I assume I've forgotten something "obvious" whilst setting up for rootless containers, or redirecting ports, or something of that nature?

2 2

podman & pi, architecture confusion
by Brian Fallik 11 Feb '20

11 Feb '20

Hi, I've been actively following the work to package Podman for Debian for eventual installation on my raspberry pi nodes. I noticed the installation docs recommended using the Kubic project packaging and so I used that to successfully (and easily!) install podman on my raspi. Hooray! However now I'm having trouble pulling arm images. All my attempts result in amd64: # podman pull coredns/coredns:latest Trying to pull docker.io/coredns/coredns:latest... Getting image source signatures Copying blob c6568d217a00 done Copying blob 89d2da39cc12 done Copying config b52ee75a77 done Writing manifest to image destination Storing signatures b52ee75a7749dc470ec4dacf990c26733c1477371f190e2748d653b8834c3f48 # podman image inspect b52ee75a7749d | jq '.[0].Architecture' "amd64" and then again with override-arch: # podman image rm b52ee75a7749d Untagged: docker.io/coredns/coredns:latest Deleted: b52ee75a7749dc470ec4dacf990c26733c1477371f190e2748d653b8834c3f48 # podman pull --override-arch=arm coredns/coredns:latest Trying to pull docker.io/coredns/coredns:latest... Getting image source signatures Copying blob c6568d217a00 done Copying blob 89d2da39cc12 done Copying config b52ee75a77 done Writing manifest to image destination Storing signatures b52ee75a7749dc470ec4dacf990c26733c1477371f190e2748d653b8834c3f48 # podman image inspect b52ee75a7749d | jq '.[0].Architecture' "amd64" podman info: # podman version Version: 1.8.0 RemoteAPI Version: 1 Go Version: go1.11.6 OS/Arch: linux/arm Any tips on how to convince podman to pull arm images within rasbian? Thanks in advance, brian

2 5

Rolling updates with Podman
by laurent.pellegrino＠gmail.com 05 Feb '20

05 Feb '20

Hi there! I discovered Podman recently and started to use it as a great alternative to Docker. My question is about application updates. Let's say you have a pod running and you want to update the code for the app in that pod. Is there a simple manner to manage something similar to a Kubernetes rolling update? By rolling update, I mean performing an update with no service interruptions (i.e. starting a new pod running the new app version, switch the network traffic to the new pod and terminate the old pod). Kind Regards, Laurent Pellegrino

4 8

Attention any Python Fans
by Daniel Walsh 04 Feb '20

04 Feb '20

We are kicking off the Podman-py package to be used for binding against the new Podman APIV2. We basically have a skeleton at this point, but we are looking for contributions to help build out the bindings. Any contributors looking to write python code and ESPECIALLY contribute tests cases to work with the API, would be greatly appreciated. This is your chance to get in on the ground floor and start contributing. Thanks for your consideration.

1 0

Podman hanging on start, ps, and erroring out with slirp4netns on run
by Eric Gustavsson 04 Feb '20

04 Feb '20

Hi all, I have unit file generated by podman running, though as soon as I run it there's issues with running any other command that needs to do something with containers. podman ps for example will be completely unresponsive and not return anything, even after waiting minutes. Not only that, but even running podman start x by itself will hang or creating new containers This is with Fedora 30 and Kernel 5.1.8-300.fc30.x86_64 spytec@KeyraGuest1:~$ podman --version podman version 1.7.0 spytec@KeyraGuest1:~$ podman start bitwarden -a ^C spytec@KeyraGuest1:~$ sudo systemctl start bitwarden ^C spytec@KeyraGuest1:~$ sudo systemctl status bitwarden [... output omitted...] Jan 31 13:53:14 KeyraGuest1 systemd[1]: Starting Podman container-bitwarden.service... spytec@KeyraGuest1:~$ sudo systemctl stop bitwarden spytec@KeyraGuest1:~$ podman ps ^C spytec@KeyraGuest1:~$ ps auxww | grep podman spytec 1097 0.0 0.8 62816 33808 ? S 13:52 0:00 podman spytec 1171 0.0 1.3 681944 55064 ? Ssl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1178 0.0 1.4 755824 56680 ? Sl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1224 0.0 0.0 9360 880 pts/0 S+ 13:54 0:00 grep --color=auto podman spytec@KeyraGuest1:~$ journalctl -u bitwarden | tail -n 5 Jan 31 13:51:50 KeyraGuest1 systemd[1]: bitwarden.service: Failed with result 'exit-code'. Jan 31 13:51:50 KeyraGuest1 systemd[1]: Failed to start Podman container-bitwarden.service. Jan 31 13:53:14 KeyraGuest1 systemd[1]: Starting Podman container-bitwarden.service... Jan 31 13:54:26 KeyraGuest1 systemd[1]: bitwarden.service: Succeeded. Jan 31 13:54:26 KeyraGuest1 systemd[1]: Stopped Podman container-bitwarden.service. spytec@KeyraGuest1:~$ ps auxww | grep podman spytec 1097 0.0 0.8 62816 33808 ? S 13:52 0:00 podman spytec 1171 0.0 1.3 682008 55064 ? Ssl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1178 0.0 1.4 755824 56680 ? Sl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1235 0.0 0.0 9360 816 pts/0 S+ 13:55 0:00 grep --color=auto podman spytec@KeyraGuest1:~$ kill 1181 spytec@KeyraGuest1:~$ kill 1097 spytec@KeyraGuest1:~$ podman ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES baa2f3d6ed39 docker.io/bitwardenrs/server:latest /bitwarden_rs 3 weeks ago Created 0.0.0.0:8080->8080/tcp bitwarden And creating a whole new container spytec@KeyraGuest1:~$ podman run -d --name test postgres Trying to pull docker.io/library/postgres... [... output omitted...] Writing manifest to image destination Storing signatures Error: slirp4netns failed: "/usr/bin/slirp4netns: unrecognized option '--netns-type=path'\nUsage: /usr/bin/slirp4netns [OPTION]... PID TAPNAME\nUser-mode networking for unprivileged network namespaces.\n\n-c, --configure bring up the interface\n-e, --exit-fd=FD specify the FD for terminating slirp4netns\n-r, --ready-fd=FD specify the FD to write to when the network is configured\n-m, --mtu=MTU specify MTU (default=1500, max=65521)\n--cidr=CIDR specify network address CIDR (default=10.0.2.0/24)\n--disable-host-loopback prohibit connecting to 127.0.0.1:* on the host namespace\n-a, --api-socket=PATH specify API socket path\n-6, --enable-ipv6 enable IPv6 (experimental)\n-h, --help show this help and exit\n-v, --version show version and exit\n" Thanks, Eric Gustavsson, RHCSA He/Him/His Software Engineer Red Hat <https://www.redhat.com> IM: Telegram: @SpyTec E1FE 044A E0DE 127D CBCA E7C7 BD1B 8DF2 C5A1 5384 <https://www.redhat.com>

3 8

Re: podman upgrade from 1.4 to 1.7 on Redhat 7.7
by James Cassell 02 Feb '20

02 Feb '20

The packages shipped by Red Hat tend to lag the latest upstream version, almost by design. Last I checked, 1.4.4 was the latest available in RHEL 7. V/r, James Cassell On Sat, Feb 1, 2020, at 9:46 AM, José Osorio R. wrote: > > 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 > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io >

1 0