-
Bug
-
Resolution: Not a Bug
-
Medium
-
None
-
4.7, 4.8, 4.9, 4.10-1.2.0
-
None
-
False
-
False
-
-
Known Issue
-
Done
-
Kata Sprint #196
-
0
-
0
Description of problem:
From the doc:
https://docs.openshift.com/container-platform/4.6/storage/persistent_storage/persistent-storage-hostpath.html
On the kata node, create /mnt/data.
$ cat pv.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
name: task-pv-volume
labels:
type: local
spec:
storageClassName: manual
capacity:
storage: 5Gi
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Retain
hostPath:
path: "/mnt/data"
$ oc create -f pv.yaml
$ cat pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: task-pvc-volume
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: manual
$ oc create -f pvc.yaml
$ cat pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: pod-sleep
spec:
containers:
- name: pod-sleep
image: ubi8
securityContext:
privileged: true
volumeMounts: - mountPath: /data
name: hostpath-privileged
command: ["sleep"]
args: ["10000"]
securityContext: {}
volumes: - name: hostpath-privileged
persistentVolumeClaim:
claimName: task-pvc-volume
runtimeClassName: kata
$ oc create -f pod.yaml
We end up with unable to create the pod.
Warning Failed 30s (x11 over 10m) kubelet Error: CreateContainer failed: Timeout reached after 10s waiting for device 0:0:0:0/block: unknown
Version-Release number of selected component (if applicable):
kata 1.11.3-1.el8
How reproducible:
always
- is duplicated by
-
KATA-880 [kata] Regular user have no write access right to mounted pv when using kata container runtime
- Closed
- external trackers