Nalin Dahyabhai
Nalin Dahyabhai
Yes, the container image has the environment variable set in it to override the compiled-in default.
For handling `RUN` instructions, it's a combination of * Being able to create a user namespace with multiple IDs mapped into it, or being started as UID 0 and having...
When attempting to nest a container, the "host" namespaces are those being used by the container. If it runs, great. Aside: with kernel 5.11 or on RHEL 8.5 or later,...
> Unfortunately, mounting `/var/lib/containers` doesn't seem to work for me, neither locally with `podman run` nor in Kubernetes. I still get this error despite the kernels seemingly being new enough...
Outside of a container, it's usually labeled `container_runtime_exec_t`, so I would expect `container_runtime_t` to be the preferred domain to be run in.
With "inherit", the compression used for an image that did not reuse layers from a base image would still need to be decided somehow. At push-time, given that we write...
Wait, is the logic for `compression_format` only implemented in podman?
I think this will be fixed by https://github.com/containers/buildah/pull/5473, which is currently stuck on a different test in CI. Any chance you can give it a go?
Thanks! Closing this as resolved in #5473, which was in time for inclusion in 1.36.
If the bot's not going to to do it, this needs text advising _someone_ that they're expected to close the corresponding podman PR when their buildah PR is merged or...