RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1423497 - Atomic install command fails during ipa-docker image installation.
Summary: Atomic install command fails during ipa-docker image installation.
Keywords:
Status: CLOSED DUPLICATE of bug 1420591
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-17 13:06 UTC by Nikhil Dehadrai
Modified: 2019-03-06 01:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-20 09:19:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nikhil Dehadrai 2017-02-17 13:06:31 UTC 
Description of problem:
Atomic install command fails during ipa-docker image installation for Atomic host 7.3.3, but it runs successfully for Atomic host version 7.3.2.

Version-Release number of selected component (if applicable):
Atomic host version-7.3.3


How reproducible:
Always


Steps to Reproduce:
1. Setup Atomic host at version 7.3.2.
2. Pull the latest IPA-docker image and load it to Atomic host. tag this image as "ipadocker". Make directory named "ipdocker at path such as "/var/lib/ipadocker"

3. Install Latest IPA-server using ipa-docker images using command:

atomic install --name ipadocker ipadocker net-host ipa-server-install

4. Now Stop the container using command and uninstall ipa-server:

docker stop ipadocker
atomic uninstall ipadocker
rm -rf /var/lib/ipadocker

5. Now upgrade the atomic host to latest version. (In my case I used OS-tree repo) 

6. Run the command and then reboot once upgrade is completed.

rpm-ostree upgrade

7. Now login to atomic host, make directory named "ipdocker at path such as "/var/lib/ipadocker" and again try installing ipa-server using command:

atomic install --name ipadocker ipadocker net-host ipa-server-install


Actual results:
1. After step3, atomic install command is successful and ipa-server is installed via ipa-docker image successfully.
2. after step4, atomic install command fails with following error:

-bash-4.2# atomic install --name ipadocker ipadocker net-host ipa-server-install

docker run -ti --rm --privileged -v /:/host -e HOST=/host -e DATADIR=/var/lib/ipadocker -e NAME=ipadocker -e IMAGE=ipadocker ipadocker /bin/install.sh net-host ipa-server-install
+ chroot /host /usr/bin/docker run -ti --rm --name ipadocker -e NAME=ipadocker -e IMAGE=ipadocker -v /var/lib/ipadocker:/data:Z -v /sys/fs/cgroup:/sys/fs/cgroup:ro --tmpfs /run --tmpfs /tmp -v /dev/urandom:/dev/random:ro --net=host ipadocker exit-on-finished ipa-server-install
panic: standard_init_linux.go:178: exec user process caused "permission denied" [recovered]
	panic: standard_init_linux.go:178: exec user process caused "permission denied"

goroutine 1 [running, locked to thread]:
panic(0x6f3000, 0xc4200ff7a0)
	/usr/lib/golang/src/runtime/panic.go:500 +0x1a1
github.com/urfave/cli.HandleAction.func1(0xc420075748)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/urfave/cli/app.go:478 +0x247
panic(0x6f3000, 0xc4200ff7a0)
	/usr/lib/golang/src/runtime/panic.go:458 +0x243
github.com/opencontainers/runc/libcontainer.(*LinuxFactory).StartInitialization.func1(0xc420075198, 0xc42001e0c8, 0xc420075238)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/opencontainers/runc/libcontainer/factory_linux.go:259 +0x18f
github.com/opencontainers/runc/libcontainer.(*LinuxFactory).StartInitialization(0xc420047590, 0xaac9c0, 0xc4200ff7a0)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/opencontainers/runc/libcontainer/factory_linux.go:277 +0x353
main.glob..func8(0xc420078a00, 0x0, 0x0)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/main_unix.go:26 +0x66
reflect.Value.call(0x6ddd80, 0x769ce8, 0x13, 0x73c1c9, 0x4, 0xc420075708, 0x1, 0x1, 0x4d17a8, 0x732020, ...)
	/usr/lib/golang/src/reflect/value.go:434 +0x5c8
reflect.Value.Call(0x6ddd80, 0x769ce8, 0x13, 0xc420075708, 0x1, 0x1, 0xac2700, 0xc4200756e8, 0x4da786)
	/usr/lib/golang/src/reflect/value.go:302 +0xa4
github.com/urfave/cli.HandleAction(0x6ddd80, 0x769ce8, 0xc420078a00, 0x0, 0x0)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/urfave/cli/app.go:487 +0x1e0
github.com/urfave/cli.Command.Run(0x73c395, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x74d9d9, 0x51, 0x0, ...)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/urfave/cli/command.go:191 +0xc3b
github.com/urfave/cli.(*App).Run(0xc420098000, 0xc42000c120, 0x2, 0x2, 0x0, 0x0)
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/Godeps/_workspace/src/github.com/urfave/cli/app.go:240 +0x611
main.main()
	/builddir/build/BUILD/docker-dfc4aea4ba81ecbe1ff8d58f4c4b6d192f82091b/runc-81b254244390bc636b20c87c34a3d9e1a8645069/main.go:137 +0xbd6

-bash-4.2# 

Expected results:
Atomic install command should run successfully and ipa-server should get installed through ipa-docker image.
Comment 2 Lukas Slebodnik 2017-02-17 13:22:18 UTC 
It failed in "docker run". It is bug in docker and not in image.
Comment 3 Antonio Murdaca 2017-02-17 13:29:15 UTC 
Could you try re-running everything with selinux disabled?
Comment 11 Alex Jia 2017-02-20 09:19:39 UTC 

*** This bug has been marked as a duplicate of bug 1420591 ***
Note You need to log in before you can comment on or make changes to this bug.