/dev/null can't be found inside the container #1412
Comments
|
This looks like it's related to a |
|
What is the exact podman command that is causing this issue? |
|
"Error running ['podman', '--log-level=debug', 'run', '--name', 'iscsid', '--label', 'config_id=tripleo_step3', '--label', 'container_name=iscsid', '--label', 'managed_by=paunch', '--label', 'config_data={"start_order": 2, "healthcheck": {"test": "/openstack/healthcheck"}, "image": "docker.io/tripleomaster/centos-binary-iscsid:9ad93affedba8870315dd72c714770875ce24759_b72f0c42", "environment": ["KOLLA_CONFIG_STRATEGY=COPY_ALWAYS"], "volumes": ["/etc/hosts:/etc/hosts:ro", "/etc/localtime:/etc/localtime:ro", "/etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro", "/etc/pki/ca-trust/source/anchors:/etc/pki/ca-trust/source/anchors:ro", "/etc/pki/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro", "/etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust.crt:ro", "/etc/pki/tls/cert.pem:/etc/pki/tls/cert.pem:ro", "/dev/log:/dev/log", "/etc/ssh/ssh_known_hosts:/etc/ssh/ssh_known_hosts:ro", "/etc/puppet:/etc/puppet:ro", "/var/lib/kolla/config_files/iscsid.json:/var/lib/kolla/config_files/config.json:ro", "/dev/:/dev/", "/run/:/run/", "/sys:/sys", "/lib/modules:/lib/modules:ro", "/etc/iscsi:/var/lib/kolla/config_files/src-iscsid:ro"], "net": "host", "privileged": true, "restart": "always"}', '--detach=true', '--env=KOLLA_CONFIG_STRATEGY=COPY_ALWAYS', '--net=host', '--privileged=true', '--volume=/etc/hosts:/etc/hosts:ro', '--volume=/etc/localtime:/etc/localtime:ro', '--volume=/etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro', '--volume=/etc/pki/ca-trust/source/anchors:/etc/pki/ca-trust/source/anchors:ro', '--volume=/etc/pki/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro', '--volume=/etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust.crt:ro', '--volume=/etc/pki/tls/cert.pem:/etc/pki/tls/cert.pem:ro', '--volume=/dev/log:/dev/log', '--volume=/etc/ssh/ssh_known_hosts:/etc/ssh/ssh_known_hosts:ro', '--volume=/etc/puppet:/etc/puppet:ro', '--volume=/var/lib/kolla/config_files/iscsid.json:/var/lib/kolla/config_files/config.json:ro', '--volume=/dev/:/dev/', '--volume=/run/:/run |
|
Going to give this a go after lunch |
|
Why would /dev/null disappear? |
We currently hit this bug: containers/podman#1412 In order to move forward, let's bind-mount /dev/null into the container until the bug is fixed. Note, it doesn't hurt docker deployment as we already mounted /dev. Related-Bug: #1791167 Change-Id: I0e885c248bb08c04fb9b7efa9e075e692879b450
|
I would like to see a simplifier for this. |
|
@mheon ack - I'll test it asap this week. Thanks for the heads-up. |
|
@mheon I built podman from master and tried a redeploy, it's still failing. Complete trace: https://paste.fedoraproject.org/paste/Rx9jBzlH8VAw2iRUlilzow |
|
well, it's still not working: http://paste.openstack.org/show/V7VOIzpvBDLPVbBI02NS/ |
|
I haven't been able to make it work yet. I don't give up. Will update here when I'm done with this bug. |
|
Alright, we've moved from /dev/null missing to CGroups errors. That's progress, at least |
|
I bet this is related to the issues with -v /sys |
|
oh right, we moved forward indeed. I guess I'll revert my workaround. Thanks! I'll probably close the card if we can confirm it's -v /sys or next week. |
|
This is the latest results from today: "stderr: container create failed: container_linux.go:336: starting container process caused "process_linux.go:399: container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/containers/storage/overlay-containers/20c572c4fa8107b525c274c9dcf47ef57de4177d1486651ade322ab9cf78dda8/userdata/cgroup\\\" to rootfs \\\"/var/lib/containers/storage/overlay/c398946e69285ed58a50530082b05958bb2b8e1e2d9b309de022affe30dca57e/merged\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"stat /sys/fs/cgroup/systemd/machine.slice/libpod-20c572c4fa8107b525c274c9dcf47ef57de4177d1486651ade322ab9cf78dda8.scope: no such file or directory\\\"\""", |
|
Alright, this does sound like /sys - I'll keep looking into it on Monday |
|
so my iscsid container is not working at all: |
|
Could you try this with podman 0.9.2? |
|
testing today with master, will post results shortly. |
|
Huh. I still don't have /sys containers working locally, but that could be an environment issue on my end... I'll check it out on Monday. |
|
@mheon I think you are seeing a Red Herring. Or different issue. |
|
@rhatdan Agree it's a different issue, still tracking it down. I think it has something to do with our /dev/pts mount. |
github-actions
bot
added
the
locked - please file new issue/PR
/kind bug
Description
/dev/null can't be found inside the container, which is problematic for some applications like iSCSI or other services in OpenStack which require the access to /dev/null.
Steps to reproduce the issue:
Start a container which needs access to /dev/null
Describe the results you received:
From strace:
[pid 64887] stat("/dev/null", 0xc420106818) = -1 ENOENT (No such file or directory)
Full podman debug:
http://paste.openstack.org/show/hDyRznDV1Wv5K4lqNNVr/
Describe the results you expected:
Container starts correctly.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info:Additional environment details (AWS, VirtualBox, physical, etc.):
Running it in a VM managed by libvirt/kvm.
The text was updated successfully, but these errors were encountered: