Windows Server 2012下Docker Toolbox挂载RabbitMQ目录报错求助

Let’s work through that could_not_write_file error you’re hitting when trying to mount RabbitMQ’s mnesia directory for persistence. The etxtbsy part translates to "text file busy"—this usually stems from file system compatibility issues between Windows Server 2012’s NTFS and the Linux-based Docker container, or permission/locking problems with the shared directory from Docker Toolbox.

Here are practical, actionable solutions to get your persistent RabbitMQ setup working:

1. Pre-Seed the Local Directory with Correct Mnesia Files #

The empty Windows directory you’re mounting likely doesn’t have the right file structure or permissions RabbitMQ expects. Let’s copy the working mnesia files from a temporary container first:

# Start a temporary container without the problematic mount
docker run --rm -h ndvi -td ndvi temp_rabbitmq

# Copy the default mnesia directory from the container to your Windows path
docker cp temp_rabbitmq:/var/lib/rabbitmq/mnesia /c/Users/Administrator/services/ndvi-service/rabbitmq/

# Stop and clean up the temp container
docker stop temp_rabbitmq

Now your local directory has the exact file structure and permissions RabbitMQ needs. Try running your original docker run command again with the mount.

2. Adjust Mount Permissions and User Context #

RabbitMQ runs under the rabbitmq user by default, and Docker Toolbox’s shared directories sometimes have permission mismatches. Modify your run command to explicitly use the rabbitmq user and ensure read-write access:

docker run --rm -p 5050:5050 -p 49555:5555 -p 15672:15672 -m 3G \
  -v /c/Users/Administrator/services/ndvi-service/logs:/home/ndvi_logs \
  -v /c/Users/Administrator/services/ndvi-service/rabbitmq:/var/lib/rabbitmq/mnesia:rw \
  -h ndvi -u rabbitmq -td ndvi > container_id

The :rw flag guarantees read-write access, and -u rabbitmq runs the container as the user that owns the mnesia files.

3. Verify VirtualBox Shared Folder Settings #

Docker Toolbox relies on VirtualBox’s shared folders to connect Windows directories to the Linux VM. Double-check these settings:

• Open VirtualBox, find the default boot2docker VM used by Docker Toolbox.
• Go to Settings > Shared Folders.
• Ensure /c/Users is listed, with Auto-mount and Make Permanent enabled, and permissions set to Read/Write.
• If you made changes, restart the VM to apply them:

  docker-machine stop default
  docker-machine start default
  eval $(docker-machine env default)
  

4. Use Docker Volumes Instead (Recommended) #

Windows NTFS and Linux file systems don’t play perfectly together for high-I/O workloads like RabbitMQ’s mnesia. Docker volumes are managed directly by Docker and avoid these compatibility issues. Here’s how to switch:

# Create a dedicated volume for RabbitMQ data
docker volume create rabbitmq_mnesia

# Update your run command to use this volume instead of the Windows directory mount
docker run --rm -p 5050:5050 -p 49555:5555 -p 15672:15672 -m 3G \
  -v /c/Users/Administrator/services/ndvi-service/logs:/home/ndvi_logs \
  -v rabbitmq_mnesia:/var/lib/rabbitmq/mnesia \
  -h ndvi -td ndvi > container_id

Your data will persist in the Docker volume, and you can still back it up if needed using docker cp:

# Backup the volume to your Windows directory
docker run --rm -v rabbitmq_mnesia:/source -v /c/Users/Administrator/services/ndvi-service/rabbitmq-backup:/target busybox cp -a /source/. /target/

Why This Happened #

The etxtbsy error means RabbitMQ couldn’t write to the mnesia file because it was either locked by the Windows file system, or the container lacked proper permissions to modify the shared directory. Docker Toolbox’s shared folders have known quirks with file locking and permission mapping between Windows and Linux, which is why using Docker volumes is the more reliable long-term fix.

内容的提问来源于stack exchange，提问作者gustav