I created some docker droplets few months ago by choosing from the marketplace the available docker image. That created the droplets using Ubuntu 18.04.3 LTS and Docker version 19.03.1, build 74b1e89. Now I wanted to add some more droplets but it seems that the image has been upgraded to Ubuntu 20.04.1 LTS and Docker version 19.03.13, build 4484c46d9d. How can I choose the same docker version? I want to create a swarm and need same docker engine. Thank you. (I see there’s also some API to create droplets but not sure where I find same image that was in marketplace, maybe I can pass that as parameter?)

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

Hi there @Strobboscope,

A quick way to solve that problem would be to do the following:

  • Take a snapshot of your existing Droplet
  • Use that snapshot to create new Droplets

That way you will ensure that both the OS version, all configuration files, and the Docker engine version are all the same on all of your Droplets.

Hope that this helps!
Regards,
Bobby

  • Thank you for help!
    Do you have any idea if that can cause some issues with the swarm?
    I mean I need to join that new droplet in a swarm.
    Can this cause issues if everything is cloned from such a snapshot?
    Actually I nead a clone because I want same micro-service replicated on another droplet but was wondering if some cloned configs might break the swarm when I would join the new droplet to it?

    • Hi there @Strobboscope,

      I believe that once your second Droplet is up and running, you should be able to join it to the Docker Swarm either as a worker or a manager as it will have a fresh new IP address.

      Let me know how it goes!
      Regards,
      Bobby

      • It works!!!
        Thank you for your suggestion!
        I created a snapshot and then a new Droplet from it.
        I joined the new droplet in the swarm.
        For some reason, .. some settings were preserved from the cloned droplet because when I joined the new node, the swarm manager was showing only one node as joined, probably was joining with same token or something.

        So what I did was to go on the new node and force the node to leave the swarm and joined it again as worker with a new token from manager.
        This time the swarm manager showed both nodes as joined and active and it is successfully serving data from both nodes, and the default load balancer works.
        Thank you again!