improve valid_volumes instruction
This commit is contained in:
parent
a895e8ebd2
commit
fc5c076c1b
1 changed files with 6 additions and 4 deletions
|
@ -53,7 +53,9 @@ container:
|
|||
# The parent directory of a job's working directory.
|
||||
# If it's empty, /workspace will be used.
|
||||
workdir_parent:
|
||||
# Volumes (including bind mounts) can be mounted to containers.
|
||||
# This is a sequence. If the sequence is empty, any volume can be mounted.
|
||||
# Used for `jobs.<job_id>.container.volumes` or `jobs.<job_id>.services.<service_id>.volumes`
|
||||
valid_volumes:
|
||||
# Volumes (including bind mounts) can be mounted to containers. If it's empty, any volume can be mounted.
|
||||
# For example, if you only allow containers to mount the `data` volume and the `/etc/secrets` directory, you should change the config to:
|
||||
# valid_volumes:
|
||||
# - data
|
||||
# - /etc/secrets
|
||||
valid_volumes: []
|
||||
|
|
Loading…
Add table
Reference in a new issue