You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: completions/fish/crio.fish
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ function __fish_crio_no_subcommand --description 'Test if there has been any sub
10
10
end
11
11
12
12
complete-c crio -n'__fish_crio_no_subcommand'-f-l additional-devices -r-d'Devices to add to the containers '
13
+
complete-c crio -n'__fish_crio_no_subcommand'-f-l allow-userns-annotation -d'[EXPERIMENTAL] Allow usage of the annotation to setup user namespaces (default: false)'
13
14
complete-c crio -n'__fish_crio_no_subcommand'-f-l apparmor-profile -r-d'Name of the apparmor profile to be used as the runtime\'s default. This only takes effect if the user does not specify a profile via the Kubernetes Pod\'s metadata annotation.'
14
15
complete-c crio -n'__fish_crio_no_subcommand'-f-l big-files-temporary-dir -r-d'Path to the temporary directory to use for storing big files, used to store image blobs and data streams related to containers image management.'
15
16
complete-c crio -n'__fish_crio_no_subcommand'-f-lbind-mount-prefix -r-d'A prefix to use for the source of the bind mounts. This option would be useful if you were running CRI-O in a container. And had `/` mounted on `/host` in your container. Then if you ran CRI-O with the `--bind-mount-prefix=/host` option, CRI-O would add /host to any bind mounts it is handed over CRI. If Kubernetes asked to have `/var/lib/foobar` bind mounted into the container, then CRI-O would bind mount `/host/var/lib/foobar`. Since CRI-O itself is running in a container with `/` or the host mounted on `/host`, the container would end up with `/var/lib/foobar` from the host mounted in the container rather then `/var/lib/foobar` from the CRI-O container. (default: "")'
**--additional-devices**="": Devices to add to the containers (default: [])
114
115
116
+
**--allow-userns-annotation**: [EXPERIMENTAL] Allow usage of the annotation to setup user namespaces (default: false)
117
+
115
118
**--apparmor-profile**="": Name of the apparmor profile to be used as the runtime's default. This only takes effect if the user does not specify a profile via the Kubernetes Pod's metadata annotation. (default: crio-default)
116
119
117
120
**--big-files-temporary-dir**="": Path to the temporary directory to use for storing big files, used to store image blobs and data streams related to containers image management.
Copy file name to clipboardExpand all lines: docs/crio.conf.5.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,6 +206,10 @@ the container runtime configuration.
206
206
**read_only**=false
207
207
If set to true, all containers will run in read-only mode.
208
208
209
+
**allow_userns_annotation**=false
210
+
[EXPERIMENTAL] Allow usage of the experimental feature for setting user namespaces through the io.kubernetes.cri-o.userns-mode annotation. This is an experimental feature,
211
+
do not enable in production. It may be changed in the future without any notice.
212
+
209
213
**uid_mappings**=""
210
214
The UID mappings for the user namespace of each container. A range is specified in the form containerUID:HostUID:Size. Multiple ranges must be separated by comma.
Usage: fmt.Sprintf("A prefix to use for the source of the bind mounts. This option would be useful if you were running CRI-O in a container. And had `/` mounted on `/host` in your container. Then if you ran CRI-O with the `--bind-mount-prefix=/host` option, CRI-O would add /host to any bind mounts it is handed over CRI. If Kubernetes asked to have `/var/lib/foobar` bind mounted into the container, then CRI-O would bind mount `/host/var/lib/foobar`. Since CRI-O itself is running in a container with `/` or the host mounted on `/host`, the container would end up with `/var/lib/foobar` from the host mounted in the container rather then `/var/lib/foobar` from the CRI-O container. (default: %q)", defConf.BindMountPrefix),
652
655
EnvVars: []string{"CONTAINER_BIND_MOUNT_PREFIX"},
653
656
},
657
+
&cli.BoolFlag{
658
+
Name: "allow-userns-annotation",
659
+
Usage: fmt.Sprintf("[EXPERIMENTAL] Allow usage of the annotation to setup user namespaces (default: %t)", defConf.AllowUsernsAnnotation),
660
+
EnvVars: []string{"ALLOW_USERNS_ANNOTATION"},
661
+
},
654
662
&cli.StringFlag{
655
663
Name: "uid-mappings",
656
664
Usage: fmt.Sprintf("Specify the UID mappings to use for the user namespace (default: %q)", defConf.UIDMappings),
0 commit comments