DOCKER-73: sdc-docker M23: Docker image publishing support

Details

Issue Type:New Feature
Priority:4 - Normal
Status:Resolved
Created at:2015-01-06T06:08:37.000Z
Updated at:2018-05-08T02:26:24.746Z

People

Created by:Former user
Reported by:Former user
Assigned to:Former user

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2018-05-08T02:26:24.730Z)

Related Issues

Description

https://mo.joyent.com/docs/engdoc/master/roadmap/projects/sdc-docker.html#m23

Finish off docker image work. The first part of the image work was done in M2. This is for publish support to allow user to create a docker repo out of a container and push it to the registry. This fulfills three of common container lifecyle use cases - backup, snapshot and templating. See the roadmap.

Comments

Comment by Former user
Created at 2015-05-01T17:20:00.000Z

Some notes on 'docker tag' when I was looking at the "UUID change" (what the IMGAPI UUID should be a for a Docker image ID, see DOCKER-257 work):

The question was whether the UUID change to be dependent on both (a) the docker image ID and (b) on the registry host (aka the index name) would cause problems for later supporting 'docker tag'. Take this scenario

1. 'docker pull busybox:latest'
2. 'docker tag busybox:latest reg.example.com/busybox:foo'
3. 'docker push reg.example.com/busybox:foo'
4. 'docker pull reg.example.com/busybox:foo'

With Docker-docker at #2 you have:

ubuntu@1fd15fd8-e5cd-6ef0-ab35-aae2181b7cd4:~$ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
busybox latest 8c2e06607696 13 days ago 2.433 MB
localhost:5000/busybox latest 8c2e06607696 13 days ago 2.433 MB

then #4 basically becomes a no-op (already have the image locally).

How do we make this work reasonably for SDC? An attempt:


Comment by Former user
Created at 2016-11-04T22:50:28.000Z

ignore my flailing on resolved state.


Comment by Former user
Created at 2018-05-08T02:26:24.743Z

Todd has added 'docker push' support.