Howto::Docker Registry

Introduction

We offer a docker image registry service tied with https://git.cs.vt.edu that offers a place to share your docker images and version control them. This is a quick start guide on how to use our docker registry.

Create Project

First you must create a project in git.cs.vt.edu to store your images or make sure registry is enabled on an existing project. For new projects, the registry is automatically enabled. For an older project you must enable it:

1. Login into https://git.cs.vt.edu
2. Open the project
3. Go to "Settings->General"
4. Expand "Permissions"
5. Make sure "Container registry" is checked

Using Registry

These commands are run on your development machine.

Log into registry

To be able to push images up to your registry, you must log in

• docker login docker.cs.vt.edu

Build and push image

Example of building your docker image and uploading it to your registry

• Determine your image's URL with optional tag:
  • docker.cs.vt.edu/<username>/<project>/<image>:<tag>
• You tag your docker build with the image URL, example:
  • docker build -t docker.cs.vt.edu/carnold/library/hello .
• Push the image up to your registry
  • docker push docker.cs.vt.edu/carnold/library/hello

Running an image

• docker run docker.cs.vt.edu/carnold/library/hello:latest

Public vs. Internal vs. Private

Public

If your project is set as "public", this will allow anyone on the Internet to be able to download and use your images.

Internal

If your project is set as "internal", then anyone with access to git.cs.vt.edu can download and use the images after they login with their login.

Private

If your project is set as "private", then only you will be able download and use the images after you login. Unless you create a deploy token:

Deploy Token

You can create a "deploy token" that will allow anyone you share the token with to download and use your images. The user will login with your username and the token as the password. Tokens expire after a time limit. Note: once downloaded the client will have a cached copy of the images, even after the token expires. Find out more about deploy tokens: https://docs.gitlab.com/ce/user/project/deploy_tokens/index.html