Bootstrap Docker "cannot mount volume over exiting file"

Blue Robotics Software BlueOS
1

Every so often after powering off the raspberry pi the bootstrap docker container fails to create the core container.

It gives these sort of errors in the logs:

Starting bluerobotics/blueos-core
/bootstrap/bootstrap.py:189: UserWarning: Error trying to start image: 500 Server Error for http+docker://localhost/v1.41/containers/create?name=blueos-core: Internal Server Error ("cannot mount volume over existing file, file exists /var/lib/docker/overlay2/6db9954f230e7be8e61b8fc60269704a7edbaeb1cfbe7a0b1af9ddd95cb38734/merged/etc/machine-id"), reverting to default...
  warn(f"Error trying to start image: {error}, reverting to default...")
Starting bluerobotics/blueos-core
/bootstrap/bootstrap.py:189: UserWarning: Error trying to start image: 500 Server Error for http+docker://localhost/v1.41/containers/create?name=blueos-core: Internal Server Error ("cannot mount volume over existing file, file exists /var/lib/docker/overlay2/eebec0b04bb51cf597dee42acf29b26766cd46fc2ed0630fb133bf925c0283e2/merged/etc/dhcpcd.conf"), reverting to default...
  warn(f"Error trying to start image: {error}, reverting to default...")

Just wondering if there were any ideas as to why this is occurring. When I list the docker volumes, there are none, so I am not too sure why it tings it cannot mount the volume.

2

Hi @cpcp,

I don’t believe we’ve run into that before - thanks for reporting it!

So that we can try to replicate the issue, can you please specify

  1. the BlueOS version you’re running
    • it can be found at the bottom of the sidebar
  2. the hardware you’re running on
    • e.g. Raspberry Pi 3B / 4B
  3. whether you’re shutting down the Raspberry Pi before powering it off
  4. any other information you think may be relevant
    • it may help if you can upload the actual log file(s) instead of just a snippet
3
  1. BlueOS Version: heads/master-0-g956f4c4
    2.Raspberry Pi 4 Model B
  2. We are NOT shuttding down the Raspberry Pi before powering it off (we see this as possibly being a cause). However, even when using the proper “power-off” command it did happen once when rebooting it.
  3. Unfortunately, I have stopped/removed the container so I am not sure if I can still access the logs since it has been removed. I will upload them when the issue occurs again.
1 Like