Continuous Delivery with Docker and Jenkins by Rafał Leszko

Continuous Delivery with Docker and Jenkins by Rafał Leszko

Author:Rafał Leszko
Language: eng
Format: epub, mobi
Tags: COM051440 - COMPUTERS / Software Development and Engineering / Tools, COM048000 - COMPUTERS / Systems Architecture / Distributed Systems and Computing, COM046070 - COMPUTERS / Operating Systems / Linux
Publisher: Packt Publishing
Published: 2018-04-12T09:39:22+00:00


In most cases, <tag> is in the form of image/application version.

Let's tag the image to use Docker Hub:

$ docker tag ubuntu_with_python leszko/ubuntu_with_python:1

We could have also tagged the image in the build command: "docker

build -t leszko/ubuntu_with_python:1 . ".

If the repository has access restriction configured, we need to authorize it first:

$ docker login --username <username> --password <password>

It's possible to use the docker login command without parameters and Docker would ask interactively for the username and password.

Now, we can store the image in the registry using the push command:

$ docker push leszko/ubuntu_with_python:1

Note that there is no need to specify the registry address because Docker uses the naming convention to resolve it. The image is stored, and we can check it using the Docker Hub web interface available at https://hub.docker.com.



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.