Dockerfile, build it, tag it, and afterward send it to our own instance of docker registry. You could also use the same approach for any other registries (e.g: dockerhub, gitlab)
My example will be base on creating a docker image with Node 8 and Chrome browser on the board (I created it for running unit test against chrome headless).
docker login docker.example-domain.com:4567Dockerfile image. I used simple Node8 with yarn.Dockerfile.node_8 only to present how to also use it with a custom
name. If you just use the default name Dockerfile then you don't have to specify a characteristic --file flag.FROM node:8
# Use this path as the main working directory
WORKDIR /usr/src/app/client
COPY package.json ./
COPY yarn.lock ./
EXPOSE 8080
CMD yarn && yarn run startDockerfile image and tag it you have to use command:docker build --tag my-private-node-8:latest ~/workspace/directory-with-dockerfile-inside/docker run --interactive --tag my-private-node-8:latest /bin/bashdocker.example-domain.com:4567. Then you have to create an image and add the version of this image.docker tag my-private-node-8:latest docker.example-domain.com:4567/my-private-node-8:1.0.00.1.0, 0.8.1, ..., etc. It's a good practice to increase the version and update also the :latest tag regarding new version your last created image.docker push docker.example-domain.com:4567/my-private-node-8:1.0.0Dockerfile. The . at the very end of the command is important.docker build --file ./Dockerfile.node_8 -t docker.example-domain.com:4567/my-private-node-8:1.0.0 .docker exec -it docker.example-domain.com:4567/my-private-node-8:1.0.0 /bin/bash