IPA: Spawning container fails with "execv() failed"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Undecided
|
Jacob McCann |
Bug Description
When building my own IPA from https:/
-- Unit ironic-
Jun 30 13:21:17 host-192-168-50-113 systemd-
Jun 30 13:21:17 host-192-168-50-113 systemd-
Jun 30 13:21:17 host-192-168-50-113 systemd-
Jun 30 13:21:17 host-192-168-50-113 systemd-
Jun 30 13:21:17 host-192-168-50-113 systemd[1]: ironic-
Jun 30 13:21:17 host-192-168-50-113 systemd[1]: Unit ironic-
Jun 30 13:21:17 host-192-168-50-113 systemd[1]: ironic-
I then tried to do it manually and got the same error. I then started the container without running /usr/local/
host-192-168-50-113 ~ # /usr/bin/
> --share-system \
> --capability=all \
> --machine=
> --bind=/dev:/dev \
> --bind=
> --bind=/proc:/proc \
> --bind=/sys:/sys \
> --bind=
> --user=root \
> --keep-unit
Spawning container ironic_python_agent on /opt/ironic-
Press ^] three times within 1s to kill container.
root@host-
-bash: /usr/local/
root@host-
/usr/bin/python2.7
root@host-
It seems /usr/bin/python is missing. A workaround is to comment out the last 'cleanup' section in the Dockerfile (https:/
Changed in ironic: | |
assignee: | nobody → Jacob McCann (jmccann) |
status: | New → In Progress |
Changed in ironic: | |
status: | In Progress → Fix Committed |
Changed in ironic: | |
milestone: | none → 4.0.0 |
status: | Fix Committed → Fix Released |