Skip to main content

Docker Compose–Container image is not updated

Yesterday I talked about how we used Docker Compose to build and run an node.js/PostgreSQL application locally.We were using the build section inside the docker compose file to build the container image when running docker compose avoiding the need to build the container image separately.

However when using this approach we noticed that if we made changes to the code, those changes were not picked up by Docker Compose and we were running using an outdated image.

This turned out not to be a bug but requires a better understanding of the different Docker Compose commands.

Docker Compose commands

Docker Compose provides multiple commands and flags and it is important to understand the nuances between each command.

docker compose up

The command that we used so far was docker compose up, This builds the container image if the images does not exist and starts the containers. This already explains the behavior I described above

docker compose build

Another option is docker compose build. This will only build the images, without starting the containers.

docker compose up –-build

This combines the 2 options above and forces to build the image before the containers are started.  It rebuilds all images defined with a build context in your docker-compose.yml file. As it ensures your containers use the latest version of your code and Dockerfile instructions it is the perfect command to use during development when you are frequently changing your containers.

Disable caching

If the commands above don’t provide the expected result, you can go one step further and disable caching when using Docker Compose. By default Docker Compose relies on Docker's layer caching to optimize and speed up the image-building process. This caching mechanism can significantly reduce build times by reusing previously built layers. However, there are scenarios where you might want to bypass the cache and force Docker to build the image from scratch. This is where the --no-cache option comes in handy1.

There are several situations where using the --no-cache option is beneficial:

  1. Updating Dockerfile or Dependencies: If you have made changes to the Dockerfile or updated any dependencies, using --no-cache ensures that these changes are incorporated into the new build1.

  2. Ensuring Up-to-Date Images: For production deployments, rebuilding with --no-cache guarantees that you have the latest image without any stale layers1.

  3. Troubleshooting Build Failures: If you encounter mysterious build errors, using --no-cache can help eliminate caching as a potential cause1.

  4. Base Image Updates: If the base image you are using has been updated, rebuilding with --no-cache ensures that you get the latest base image code1.

To build the images without using the cache, run the following command:

docker compose build --no-cache

This command will force Docker to rebuild every layer from scratch, ignoring any cached layers. As it can result in longer build times and larger image sizes I would recommend to avoid using this option unless you experience issues with the other commands.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more