Project

General

Profile

Actions

Idea #13794

open

Build Docker images without requiring Docker on client

Added by Peter Amstutz over 6 years ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
Story points:
-
Release:
Release relationship:
Auto

Description

See Build docker images as part of a workflow

Web-only users do not have access to Docker on the client (in addition, some shell users don't have access to Docker for security reasons, for example visitors to cloud.curoverse.com). Ther should be a mechanism to submit a request to build a Docker image for use in Arvados.

Possible solutions:

Unprivileged build inside a normal container request

For building images, here is a blog post which outlines how to do it with nested unprivileged containers, which is described as an "epic yak shave".

This seems like it would require quite a lot of tooling development.

Special container request

Special format container request recognized by crunch-run which executes "docker build" (instead of docker run) and produces the image collection as output.

Dedicated docker builder service

New microservice with API to request "build image".

Use external build service

For example, quay.io, then pull the resulting image (#11724). Requires integrating with external service(s) so would be harder to fully automate compared to Arvados-based solutions.


Related issues

Related to Arvados Epics - Idea #16447: Improve container image handlingIn Progress12/31/202406/30/2025Actions
Related to Arvados - Idea #11724: Pull Docker images without requiring Docker on clientResolvedTom Clegg12/06/2022Actions
Blocked by Arvados - Feature #19846: Use collection properties instead of links to tag docker imagesNewTom CleggActions
Actions #1

Updated by Peter Amstutz over 6 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Peter Amstutz over 6 years ago

  • Description updated (diff)
  • Status changed from In Progress to New
Actions #3

Updated by Peter Amstutz over 6 years ago

  • Related to Idea #11724: Pull Docker images without requiring Docker on client added
Actions #4

Updated by Peter Amstutz over 6 years ago

  • Tracker changed from Bug to Feature
Actions #5

Updated by Peter Amstutz over 6 years ago

  • Tracker changed from Feature to Idea
Actions #6

Updated by Peter Amstutz over 3 years ago

  • Target version deleted (To Be Groomed)
Actions #7

Updated by Peter Amstutz about 2 years ago

  • Related to Idea #16447: Improve container image handling added
Actions #8

Updated by Tom Clegg almost 2 years ago

  • Related to deleted (Idea #11724: Pull Docker images without requiring Docker on client)
Actions #9

Updated by Tom Clegg almost 2 years ago

  • Is duplicate of Idea #11724: Pull Docker images without requiring Docker on client added
Actions #10

Updated by Tom Clegg almost 2 years ago

  • Is duplicate of deleted (Idea #11724: Pull Docker images without requiring Docker on client)
Actions #11

Updated by Tom Clegg almost 2 years ago

  • Related to Idea #11724: Pull Docker images without requiring Docker on client added
Actions #12

Updated by Tom Clegg almost 2 years ago

  • Description updated (diff)
Actions #13

Updated by Tom Clegg almost 2 years ago

  • Blocked by Feature #19846: Use collection properties instead of links to tag docker images added
Actions #14

Updated by Peter Amstutz almost 2 years ago

  • Release set to 60
Actions #15

Updated by Peter Amstutz 9 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF