Actions
Bug #7695
open[API] Accept collection UUID as a job's docker_image constraint
Story points:
0.5
Release:
Release relationship:
Auto
Description
This behavior should work identically to specifying a collection's portable data hash: if the user can read the collection, and it contains a single file that looks like a Docker image, record the Docker image's content address as the job's docker_image_locator.
Update the Collection.find_all_for_docker_image method to recognize and accept collection UUIDs, just like it recognizes collection PDHs. Apply the same conditions to accepting those collections: look at the manifest text, and confirm it contains a single .tar file that looks like a Docker image.
Update the docker_image documentation in /doc/user/topic/arv-docker.html
and /doc/api/schema/Job.html
to note that collection UUIDs are accepted.
Updated by Brett Smith about 9 years ago
- Description updated (diff)
- Story points set to 0.5
Updated by Brett Smith about 9 years ago
- Target version set to Arvados Future Sprints
Updated by Jiayong Li over 8 years ago
- Target version changed from Arvados Future Sprints to 2016-03-30 sprint
Updated by Radhika Chippada over 8 years ago
- Target version changed from 2016-03-30 sprint to Arvados Future Sprints
Updated by Ward Vandewege over 3 years ago
- Target version deleted (
Arvados Future Sprints)
Actions