Feature #19860
openSupport "pull image" container request
Description
See Build docker images as part of a workflow
A container request like this
container_request:
container_image: "arvados/builtin"
command: ["docker", "pull", "examplerepo:tag"]
mounts: {}
runtime_constraints:
API: true
RAM: 1000000000
output_path: "/"
should pull the indicated image from docker hub and save it to a collection, appropriately tagged, so it can be used in a container request like this
container_request:
container_image: "examplerepo:tag"
# ...
Related issues
Updated by Tom Clegg almost 2 years ago
- Related to Idea #16447: Improve container image handling added
Updated by Tom Clegg almost 2 years ago
- Blocked by Feature #19846: Use collection properties instead of links to tag docker images added
Updated by Peter Amstutz over 1 year ago
- Target version changed from Future to To be scheduled
Updated by Peter Amstutz over 1 year ago
- Target version changed from To be scheduled to Development 2023-05-10 sprint
Updated by Tom Clegg over 1 year ago
- Blocked by deleted (Feature #19846: Use collection properties instead of links to tag docker images)
Updated by Tom Clegg over 1 year ago
- Related to Feature #19846: Use collection properties instead of links to tag docker images added
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-05-10 sprint to Development 2023-05-24 sprint
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-05-24 sprint to Development 2023-06-07
Updated by Tom Clegg over 1 year ago
- Related to Idea #11724: Pull Docker images without requiring Docker on client added
Updated by Tom Clegg over 1 year ago
19860-docker-pull-container @ 42b266e3667f08b219173c6eb148e1a5500046c1 -- developer-run-tests: #3656
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-06-07 to Development 2023-06-21 sprint
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-06-21 sprint to To be scheduled
Updated by Peter Amstutz over 1 year ago
- Target version changed from To be scheduled to Development 2023-06-21 sprint
Updated by Peter Amstutz over 1 year ago
Make sure to update the "revision" field in the discovery document. (arvados/services/api/app/controllers/arvados/v1/schema_controller.rb)
Updated by Brett Smith over 1 year ago
- Blocks Feature #20622: arv-keepdocker uses new "pull image" API added
Updated by Brett Smith over 1 year ago
To think about: what's the user experience like when you submit a pull request, then submit a container that uses that image before the pull request has been run?
Updated by Tom Clegg over 1 year ago
- Assigned To changed from Tom Clegg to Brett Smith
Some notes about the branch in #note-16
Creates an exception to the rule that a container record's container_image
must be a PDH: now it can also be "arvados/builtin". I considered using md5("") as the builtin image to preserve the PDH rule, but I think "arvados/builtin" wins by being less mysterious.
If the configured container runtime is singularity instead of docker, you just can't use the "pull image" feature. Another alternative would be to run docker to pull images if the docker executable is available, even when configured to use singularity for running containers. And possibly another config to disable this, because it's annoying to pay/wait for an instance to come up only to find out that pull isn't supported on this cluster.
Updated by Peter Amstutz over 1 year ago
FWIW I believe singularity can pull and convert images natively, so we could have an alternate implementation for singularity. However, we currently treat singularity images as a cached conversion of a docker image and not a source of truth, which makes it impossible to have a completely Dockerless system.
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-06-21 sprint to Development 2023-07-05 sprint
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-07-05 sprint to Development 2023-07-19 sprint
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-07-19 sprint to Development 2023-08-02 sprint
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2023-08-02 sprint to Development 2023-08-16
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2023-08-16 to Development 2023-08-30
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2023-08-30 to To be scheduled
Updated by Peter Amstutz 10 months ago
- Target version changed from To be scheduled to Development 2024-01-17 sprint
Updated by Peter Amstutz 10 months ago
- Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
Updated by Peter Amstutz 10 months ago
- Target version changed from Development 2024-01-31 sprint to Development 2024-02-14 sprint
Updated by Peter Amstutz 10 months ago
- Target version changed from Development 2024-02-14 sprint to Development 2024-02-28 sprint
Updated by Peter Amstutz 8 months ago
- Target version changed from Development 2024-02-28 sprint to Development 2024-03-27 sprint
Updated by Peter Amstutz 8 months ago
- Target version changed from Development 2024-03-27 sprint to Development 2024-04-10 sprint
Updated by Peter Amstutz 7 months ago
- Target version changed from Development 2024-04-10 sprint to Development 2024-05-08 sprint
Updated by Peter Amstutz 6 months ago
- Target version changed from Development 2024-05-08 sprint to Development 2024-06-05 sprint
Updated by Peter Amstutz 6 months ago
- Target version changed from Development 2024-06-05 sprint to Future