Closed jianzhangbjz closed 1 day ago
if I understand correctly you are trying to run a nested container. Please use the same configuration as the podman container (quay.io/podman/stable:latest
), you can grab it from the /etc/containers/containers.conf
file
Thanks! But, no. I'm building a multi-arch image. I guess I need to install the qemu-system-x86_64
first.
[cloud-user@preserve-olm-env2 opm]$ podman machine init
Error: exec: "qemu-system-x86_64": executable file not found in $PATH
A friendly reminder that this issue had no activity for 30 days.
Note podman machine is not supported in RHEL AFAIK. If you have a problem with the proper builds in RHEL where crun is not working please file these bugs through the proper Red Hat channels not upstream.
Issue Description
I got the permission error by using the default runtime
runc
, as follows,And then, I followed the suggestion from https://github.com/containers/podman/issues/15314 to use the
crun
runtime, but got the below error.Steps to reproduce the issue
Steps to reproduce the issue
Configure the entrypoint and command
ENTRYPOINT ["/bin/opm"] CMD ["serve", "/configs", "--cache-dir=/tmp/cache"]
Copy declarative config root into image at /configs and pre-populate serve cache
ADD catalog /configs RUN ["/bin/opm", "serve", "/configs", "--cache-dir=/tmp/cache", "--cache-only"]
Set DC-specific label for the location of the DC root directory
in the image
LABEL operators.operatorframework.io.index.configs.v1=/configs
Describe the results you expected
Podman builds multi-arch images successfully.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting