Description of problem:
Rootless Podman segfaults when attempting to create a pod using the '--pod=new:' option for 'podman create' and 'podman run'
Version-Release number of selected component (if applicable):
podman 1.0.0
How reproducible:
100%
Steps to Reproduce:
1. As a normal user, run 'podman run -t -i --rm --pod=new:test1 fedora bash'
Actual results:
Podman segfaults
Expected results:
Podman successfully runs bash in a new container in a new pod
Additional info:
Works as expected for Podman as root
Originally tracked at https://github.com/containers/libpod/issues/2124
This is a pretty nasty segfault, and in a feature we explicitly called out in the 1.0 release notes. It's fixed upstream, so a backport shouldn't be a problem.
@Lokesh - backports to the 1.0 branch aren't done yet, will ping when they are available. The branch in question will definitely be https://github.com/containers/libpod/tree/v1.0 though
Can reproduce with podman-1.0.0-1.git82e8011.module+el8+2696+e59f0461.x86_64.rpm. And test with podman-1.0.0-2.git921f98f.module+el8+2784+9a0c1dfe.x86_64 the steps in comments #1 passed. So set this to verified. Details:
$ podman run -t -i --rm --pod=new:test1 fedora bash
[root@a6188878f326 /]# ls
bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var