`ContainerInvalidSettings` when using `--pull=always`
Open
feature request
- Dominant language
- No language data
- Stars
- 27
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
When launching a task with `container_run_options='--rm --pull=always --workdir=/app'`. The task fails with a `ContainerInvalidSettings` error. Saying the `--pull=always` is not valid. Is this behaviour blocked on purpose, or is this a bug?
Contributor guide
Assessment
This issue has not been assessed yet.