Docker: updating image and registry

What is the right workflow of updating and storing images?

For example:

  • Can you use nginx reverse proxy to docker containers without exposing any ports?
  • Cannot mount volume in docker
  • Can't delete pods in pending state?
  • Docker OSX port mapping error when run: exec
  • Ruby OOM in container
  • Docker container behavior when used in production
    1. I download source code from Github (project with Dockerfiles, docker-compose.yml)
    2. I run “docker build”
    3. And I push new image to Docker Hub (or AWS ECR)
    4. I make some changes in source code
    5. Push changes to Github
    6. And what I should to do now to update registry (Docker Hub)?

    A) Should I run again “docker build” and then push new image (with new tag) to registry?

    B) Should I somehow commit changes to existing image and update existing image on Docker Hub?

  • Docker warning on cgroup swap limit, memory.use_hierarchy
  • Docker CNI: Failed to setup network
  • Docker environment variable security
  • Adding docker to django project: no such file or directory
  • Is there a clever way to do this with Docker (maybe via save/load/diff)?
  • Change hostname after running a container
  • One Solution collect form web for “Docker: updating image and registry”

    This will depend on what for you will use your docker image and what “releasing” policy you adopt.

    My recommandation is that you sync the tags you keep on Docker Hub with the release/or tags you have in github and automate as much as you can your production with a continuous integration tools like jenkins and github webooks.

    Then your flow becomes :
    you do your code modifications and integrate them in github ideally using a pull request scheme. This means your codes will be merged into your master branch.
    Your jenkins is configured so that when master is changed it will build against your docker file and push it to Docker hub. This will erase your “latest” tag and make sure your latest tag in docker hub is always in synch with your master release on github

    If you need to keep additionnal tags, this will be typically because of different branches or relases of your software. You ‘ll do the same as above with the tag hooked up thru jenkins and github webhooks with a non master branch. For this lone, take a look as how the official libraries are organized on github (for exeample on postgres or mysql images).

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.