-
Notifications
You must be signed in to change notification settings - Fork 70
no able to perform a dnf update in a fedora container #868
Comments
I suspect this is the mmap issue that is iirc related to 9p. |
This does indeed look like the old 🌰 intel/cc-oci-runtime#669. |
(See intel/cc-oci-runtime#669 (comment) for the ramfs workaround). |
this issue was fixed in qemu 2.10 (last time I tested) :) |
@jodh-intel - that 'old' fix will no longer work as we have tightened the privs in the CC containers, so you cannot do the mount from inside the container any more :-) The 'new' fix (workaround) is to try and point the apps to use an existing tmpfs in the container for their tmp space:
@devimc - so, that begs the question - do you know when that will land into a version of CC ? |
Hi @grahamwhaley - I think this should be captured atleast in the wiki, but ideally in https://github.com/clearcontainers/runtime/blob/master/docs/limitations.md. |
Both of the netmon and proxy should use the right path figured out from the configure instead of the default settings to get their versions. Fixes: clearcontainers#868 Signed-off-by: Fupan Li <lifupan@gmail.com>
It is not possible to do an update in a fedora container
docker run -td --name test fedora sh
docker exec test sh -c "dnf -y update"
BDB0126 mmap: Invalid argument
Configurations:
cc-runtime : 3.0.10
commit : 3d402d1
OCI specs: 1.0.0-dev
Docker 1.17.09
The text was updated successfully, but these errors were encountered: