Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1380685 +++
Description of problem:
I got back to docker after a long while and when I was going to run an image, I issued "docker run" command with swapped "IMAGE" and "-it" arguments, so I got command like the following:
# docker run fedora -it /usr/bin/bash
The command failed and I was sure there is a bug in docker because it printed out:
/usr/bin/docker-current: Error response from daemon: oci runtime error: exit status 1:.
There was no sign that docker tried to interpret "-it" as COMMAND
Version-Release number of selected component (if applicable):
docker-1.12.1-28.git9a3752d.fc26.x86_64
How reproducible:
Always
Steps to Reproduce:
1. # docker run fedora fdjalsjlhglajsfd
2.
3.
Actual results:
/usr/bin/docker-current: Error response from daemon: oci runtime error: exit status 1:.
Expected results:
'fdjalsjlhglajsfd' command not found
--- Additional comment from Antonio Murdaca on 2016-09-30 06:58:05 EDT ---
I'll take a look at this shortly but this seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1379706 which should have been fixed in build 28.
--- Additional comment from Antonio Murdaca on 2016-09-30 06:59:43 EDT ---
Can you disable selinux and try again please?
--- Additional comment from Jakub Filak on 2016-09-30 07:33 EDT ---
[root@photon ~]# setenforce 0
[root@photon ~]# getenforce
Permissive
[root@photon ~]# MARK=$(date +"%F %H:%M:%S")
[root@photon ~]# docker run fedora -ti /usr/bin/bash
/usr/bin/docker-current: Error response from daemon: oci runtime error: exit status 1:.
[root@photon ~]# journalctl --since="$MARK" > /tmp/journald.txt
--- Additional comment from Antonio Murdaca on 2016-09-30 07:44:44 EDT ---
Thanks, I'll spin up a Rawhide vm and test this out.
--- Additional comment from Antonio Murdaca on 2016-10-17 07:45:02 EDT ---
This is an issue with "oci-register-machine" hook rather than a docker issue:
$ docker run busybox -ti sh
docker: Error response from daemon: oci runtime error: exit status 1:.
$ sudo mv /usr/libexec/oci/hooks.d/oci-register-machine /tmp/oci-register-machine
The command above will prevent docker from running that hook, try re-running the original command now:
$ docker run busybox -ti sh
docker: Error response from daemon: oci runtime error: exec: "-ti": executable file not found in $PATH.
Now you can see the useful "executable file not found in $PATH" error.
--- Additional comment from Daniel Walsh on 2016-10-17 11:56:24 EDT ---
This looks like an old problem we had where the pid did not exist when oci-register-machine is called. Which is not supposed to happen when using runc?
--- Additional comment from Daniel Walsh on 2016-10-17 11:58:09 EDT ---
Actually it looks like the problem is on Terminate.
Oct 17 11:56:44 dhcp-10-19-62-196.boston.devel.redhat.com oci-register-machine[31825]: 2016/10/17 11:56:44 Register machine: prestart b80799775658cf7cf95c75634a3a6f2f9f0a7196d346d94e3b075468f0919547 31807 /var/lib/docker/overlay2/3725ea6691c2a35bd0be05db96084424fa0cb77c3d9505c9f505d522eedeae61/merged
Oct 17 11:56:44 dhcp-10-19-62-196.boston.devel.redhat.com oci-register-machine[31840]: 2016/10/17 11:56:44 Register machine: poststop b80799775658cf7cf95c75634a3a6f2f9f0a7196d346d94e3b075468f0919547 0 /var/lib/docker/overlay2/3725ea6691c2a35bd0be05db96084424fa0cb77c3d9505c9f505d522eedeae61/merged
Oct 17 11:56:44 dhcp-10-19-62-196.boston.devel.redhat.com oci-register-machine[31840]: 2016/10/17 11:56:44 TerminateMachine failed: No machine 'b80799775658cf7cf95c75634a3a6f2f9f0a7196d346d94e3b075468f0919547' known
I think we need to check if the return from systemd is the UUID does not exist, just exit without a message.
--- Additional comment from Daniel Walsh on 2016-10-17 13:39:43 EDT ---
https://github.com/projectatomic/oci-register-machine/pull/28 should fix this bug.
--- Additional comment from Daniel Walsh on 2016-10-18 11:43:10 EDT ---
Fixed in oci-register-machine-0-2.7.gitbb20b00.fc26
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2893.html