Docker using private registry

There is an easy way to define Docker container using Dockerfile, you may find it in previous article. There I installed ActiveMQ to Vagrant in Docker without using any registry. The other way to do it is private Docker registry. I will install now MongoDB in a Docker container w/o Dockerfile.

First we need to prepare private registry. I have a system with docker installed and I’m just running registry and registry-ui containers there:

docker run -d -p 5000:5000 registry
docker run -d -p 8080:8080 atcol/docker-registry-ui

Than I need to add registry url in registry ui. In (that’s my host) I’m adding new registry (url:, version: v1).

Next step is installing MongoDB into ubuntu container:

docker run -t -i --name mongo ubuntu /bin/bash

And something like: apt-get install mongodb inside docker shell. After that I need to create Docker image from current container:

docker commit -m "first commit" mongo
docker rm mongo
docker run --name mongo -d -p 27017:27017 -v /data --entrypoint /usr/bin/mongod --dbpath /data
docker commit -m "first commit" mongo

Here I’m creating a image from mongo container. That I define some default variables like expose for 27017 port, volume /data and /usr/bin/mongod with --dbpath /data arguments as entry point. That means new mongo container will start mongo service with /data/ shared volume and 27017 port, mapped to the host system.

Volume /data means that this dir inside container basically is not part of that container. You can share volumes between different containers and you can map volume to specific host folder. I will do that late.

Now I need to push my image into registry: docker push You can also specify tag like if you need to save that version forever. To update I just need to change stuff inside that container and commit into image with the same name.

On my target machine I’m executing:

docker pull
docker run -d -p 27017:27017 -v /var/data:/data

So it will download the container and run it. And it will store all mongo data into /var/data host folder. So I can do whatever I want with container and be not afraid about my real data.

That’s it. I can now add this container into my Vagrant file or deploy it directly to real system.

One thought on “Docker using private registry

  1. I have a vagrantfile which was creating a VM in aws. After That I was using docker provisioner which installs tutum\mysql image on that VM. Now since we need to use our custom docker registry for image pulling, please suggest me how can I do it. Also how can I install the certificate in the VM through vagarnt file. The image can be pulled from the new docker registry as below.

    docker pull

    Please find below vagrant file

    Vagrant.configure("2") do |config| = “ubuntu_aws”
    config.vm.box_url = “”
    config.vm.synced_folder “../.”, “/vagrant”, id: “vagrant-root”, type: “docker”,disabled: true
    config.vm.provider :aws do |aws, override|
    aws.keypair_name = “XXX-key-pair”
    override.ssh.private_key_path = “C:/Users/XXX/Desktop/ppk/XXX-key-pair.pem”
    aws.access_key_id = “XXXXXXXXX”
    aws.secret_access_key = “xxxxxxxxxx”
    aws.instance_type = “t2.micro”
    aws.security_groups = [“sg-xxxxxx”]
    aws.ami = “ami-xxxxxx”
    override.ssh.username = “ubuntu”
    aws.subnet_id = “xxxxxxx”

    aws.tags = {
    'Name' => 'XXX-test',


    config.vm.provision “docker” , images:[“tutum/mysql”,”dockerfile/redis”]

    config.vm.provision “docker” do |d| “tutum/mysql”,args: “-p 3306:3306” “dockerfile/redis”,args: “-p 6379:6379”


Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see