-2

I've been looking into Docker for an easy way to scale an app. It's an React and Node app with ArangoDB database. I figured the best way to launch Arango was in a Docker and perhaps put the app and back-end in their own Docker images. However, realizing that this might require making my own private Docker registery makes adds an extra step that might be a little too much.

I liked the GUI of Jelastic, but if a Docker registry is really necessary I may go back to my Dokkku solution.

I don't suppose there is a way to use the official Node Docker image and then git clone my private repo into that?

tgogos
  • 16,343
  • 14
  • 77
  • 108
Noah
  • 3,607
  • 7
  • 33
  • 50
  • I'm not %100 sure if the official docker images are safe to use in a production environment, but at least I would't utilize them on front facing containers. just because they are same configuration and available to everyone. so everyone -including hackers- aware of default configuration. – Yarimadam Apr 17 '18 at 05:42
  • 1
    You do not have to place images on any registry. You can just use a dockerfile to locally build whatever image you wan't from the official node docker image. (Like tell in the docker file that you want the node image, and then that you would like to clone in your git repo.) You could also use [Docker Compose](https://docs.docker.com/compose/) – the_cheff Apr 17 '18 at 06:13
  • probably use docker compose - however you can build your app on top of a wildly use `node docker` image – Denis Tsoi Apr 17 '18 at 09:55

2 Answers2

2

If you suddenly decide to use the private registry - in Jelastic Cloud you can set up your own Docker private registry, build custom docker images, pull created images into the custom registry and then deploy Docker containers.

All the necessary information and steps you can find in the docs below:

Jelastic
  • 1,763
  • 1
  • 8
  • 13
0

However, realizing that this might require making my own private Docker registery makes adds an extra step that might be a little too much.

This is not correct. You do not need to run your own registry in order to use a custom Docker image; you can place that image on any existing public (or private) registry such as the ones operated by Docker (Docker Hub) or CoreOS (Quay)

If that is your only concern, I would suggest that using your own custom image on one of those hosted registry services (free or paid, public or private, as your needs require) would be one of the easiest options for you.

Damien - Layershift
  • 1,289
  • 7
  • 13