No volume mounting after Docker Desktop update

Docker Desktop
1

I updated Docker Desktop to 4.39.0. When I wanted to run docker compose up, the container didn’t start. Since then I updated to 4.40.0, but the problem persist.

My compose.yaml is super simple:

services:
  site:
    environment:
      - JEKYLL_ENV=docker
    command: jekyll serve --config _config.yml,_config.docker.yml --incremental --force_polling
    image: jekyll/jekyll:latest
    volumes:
      - .:/srv/jekyll
    ports:
      - 4000:4000
      - 35729:35729

The error message is: “Fatal: The configuration file ‘/srv/jekyll/_config.yml’ could not be found.”

It did work before the update. It had been working for years. I haven’t changed anything in the compose.yaml file.

I’m using Mac OS Sonoma 14.7, Intel Core i9 chip and Docker Desktop 4.40.0. Virtual Machine Options is Apple Virtualization framework, VirtioFS.

Please let me know if you need more information.

Any help is greatly appreciated!

2

Just to ensure the problem is really with mounting, what’s your output when running docker compose run --rm site ls /srv/jekyll?

3

Not much:

✔ Network REPONAME_default Created

4

Then it really does seem to be a mounting problem.
I think you should try downgrading back to 4.38 and see if the error persists

I also use a Mac, configured close to yours: Sequoia 15,7, i9 chip, Apple Virtualization framework - VirtioFS
In both Docker Desktop 4.39 and 4.40, I experience no problem bind-mounting

5

I downgraded to 4.38, and it’s working again. The update messes up something badly.

Thank you for the advice, I appreciate your help!

6

While it helps the immediate problem, it doesn’t solve your inability to update to a later version now, I hope this will be resolved and you won’t be stuck on 4.38, but I wouldn’t know how to continue from here - good luck!

1 Like
7

A post was split to a new topic: Environment variables are not interpreted in volume driver options in a compose file in Docker Desktop 4.40

8

I’m having a similar problem. I had a working Kubernetes environment with Docker Desktop 4.38, but all the volume mounts failed with 4.39. 4.40 has not fixed the problem. With 4.39 I completely rebuilt my Kubernetes environment, but there was no change. Downgrading to 4.38 was the only thing that worked. The errors are that the host directories do not exist, which they obviously do, and obviously they’re properly configured in Docker Desktop as they work just fine in 4.38. If anything is being logged beyond the Kubernetes container logs, I haven’t found it, but I’d welcome suggestions as to where to look.

9

You can report that on GitHub if it was not reported yet

For troubleshooting and diagnostics, you can check the this documentation