podman: podman failing in Travis CI again, now with write /proc/self/attr/keycreate: invalid argument

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Attempt to run podman build on Travis CI’s Ubuntu Xenial fails with

container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"write /proc/self/attr/keycreate: invalid argument\"

Steps to reproduce the issue:

  1. In .travis.yml, install podman using sudo add-apt-repository -y ppa:projectatomic/ppa && sudo apt-get update -y && sudo apt-get install -y podman
  2. Run sudo podman build for some Dockerfile, for example using https://github.com/adelton/freeipa-container/tree/podman

Describe the results you received:

https://travis-ci.org/adelton/freeipa-container/jobs/512956513 failed with

STEP 4: RUN groupadd -g 288 kdcproxy ; useradd -u 288 -g 288 -c 'IPA KDC Proxy User' -d '/var/lib/kdcproxy' -s '/sbin/nologin' kdcproxy
error running container: error creating container for [/bin/sh -c groupadd -g 288 kdcproxy ; useradd -u 288 -g 288 -c 'IPA KDC Proxy User' -d '/var/lib/kdcproxy' -s '/sbin/nologin' kdcproxy]: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"write /proc/self/attr/keycreate: invalid argument\"

Describe the results you expected:

The same build not failing, for example https://travis-ci.org/adelton/freeipa-container/jobs/508818334.

Additional information you deem important (e.g. issue happens only occasionally):

It is a regression.

Output of podman version:

No way to run podman version but the Travis CI log says

Unpacking cri-o-runc (1.0.0-rc6-1~ubuntu16.04.2~ppa74) ...
Selecting previously unselected package podman.
Preparing to unpack .../podman_1.2.0-1~ubuntu16.04.2~ppa14_amd64.deb ...
Unpacking podman (1.2.0-1~ubuntu16.04.2~ppa14) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up conmon (0-1~dev~ubuntu16.04~ppa2) ...
Setting up containers-golang (0.1-1~dev~ubuntu16.04~ppa1) ...
Setting up containers-common (0.1.36-1~dev~ubuntu16.04.2~ppa9) ...
Setting up libgpgme11:amd64 (1.6.0-1) ...
Setting up containernetworking-plugins (0.7.3-1~ubuntu16.04.2~ppa2) ...
Setting up cri-o-runc (1.0.0-rc6-1~ubuntu16.04.2~ppa74) ...
Setting up podman (1.2.0-1~ubuntu16.04.2~ppa14) ...

Output of podman info --debug:

N/A

Additional environment details (AWS, VirtualBox, physical, etc.):

Travis CI.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (16 by maintainers)

Most upvoted comments

According to https://bodhi.fedoraproject.org/updates/FEDORA-2019-bc70b381ad it should be in stable now. Well it reached that state yesterday.

runc should be available in updates-testing and be released by early next week.

Yes, I got the fix merged this morning, and they were waiting for the fix for rc8/