Replies: 7 comments 3 replies
-
I assume this is running podman inside a container, it is not going to work unless the outer container gives the necessary permission. |
Beta Was this translation helpful? Give feedback.
-
What is preventing |
Beta Was this translation helpful? Give feedback.
-
Update: cat << EOF > containers.conf
[containers]
netns="host"
ipcns="host"
default_sysctls = [] # Workaround
EOF podman run -it registry.access.redhat.com/ubi9/ubi-minimal Error: crun: mount `proc` to `/proc`: Permission denied: OCI permission denied |
Beta Was this translation helpful? Give feedback.
-
@Luap99 Did you intend to close this issue? |
Beta Was this translation helpful? Give feedback.
-
The mount of /proc is not an SELinux issue. The problem is you are trying to mount /proc with different options then the parent /proc, which is causing the issue. You need to mount the /proc from the host into the container. @giuseppe knows the issue. |
Beta Was this translation helpful? Give feedback.
-
the kernel requires a proc mount to be fully visible before it allows mounting a new procfs. Inside your container the |
Beta Was this translation helpful? Give feedback.
-
@giuseppe @rhatdan @umohnani8 I feel like I've almost got this working, but for the I'm trying to take advantage of Here's where I'm at so far: Create the apiVersion: apps/v1
kind: DaemonSet
metadata:
name: fuse-device-plugin-daemonset
namespace: kube-system
spec:
selector:
matchLabels:
name: fuse-device-plugin-ds
template:
metadata:
labels:
name: fuse-device-plugin-ds
spec:
nodeSelector:
node-role.kubernetes.io/worker: ""
hostNetwork: true
containers:
- image: quay.io/cgruver0/che/fuse-device-plugin:v1.1
name: fuse-device-plugin-ctr
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
volumeMounts:
- name: device-plugin
mountPath: /var/lib/kubelet/device-plugins
volumes:
- name: device-plugin
hostPath:
path: /var/lib/kubelet/device-plugins
imagePullSecrets:
- name: registry-secret Enable cat << EOF | butane | oc apply -f -
variant: openshift
version: 4.12.0
metadata:
labels:
machineconfiguration.openshift.io/role: worker
name: subuid-subgid
storage:
files:
- path: /etc/subuid
mode: 0644
overwrite: true
contents:
inline: |
core:100000:65536
containers:200000:268435456
- path: /etc/subgid
mode: 0644
overwrite: true
contents:
inline: |
core:100000:65536
containers:200000:268435456
EOF When I create a pod, I get the error: Error: crun: mount `proc` to `/proc`: Permission denied: OCI permission denied Because I don't know what to do about Can you offer any guidance? Cheers |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
Eclipse Che version 7.63 (Upstream of OpenShift Dev Spaces)
OpenShift 4.12 (OKD - Community supported OpenShift)
Fedora CoreOS 37.20230218.3.0
Kernel: 6.1.11-200.fc37.x86_64
Podman in an Eclipse Che workspace can pull images, and build images. It fails to run containers.
Output:
Steps to reproduce the issue
Steps to reproduce the issue
container-build
scc in Eclipse Chepodman run -it registry.access.redhat.com/ubi9/ubi-minimal
Describe the results you received
Describe the results you expected
Shell into a running container
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Eclipse Che 7.63
OKD 4.12
Fedora CoreOS 37.20230218.3.0
Kernel: 6.1.11-200.fc37.x86_64
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Beta Was this translation helpful? Give feedback.
All reactions