docker - 没有没有谁在MacOS+Toolbox下部署mysql并且成功挂载volume的？

Question

我是在MacOS下用Docker Toolbox，部署mysql，并且挂载了一个volume到/var/lib/mysql，但是启动容器的时候，报错。感觉和volume的权限相关。
具体错误展现如下：

迷茫 · Answer

I encountered this problem before. If it is mounted on Windows, is it because you have not mounted the disk into the virtual machine? If it has been mounted, you need to pay attention to whether the permissions are configured correctly. Correct the corresponding settings in the Dockerfile. Use the usermod command to modify the group or user permissions of the file in the directory.

If you still have any questions, please feel free to contact me and I should be able to help you solve it!

迷茫 · Answer

Most of the things developed under Mac, I put them all in the virtual machine, and then use the Mac terminal to remotely connect to the virtual machine. Many development servers such as nginx, mongodb, mysql, apache, docker, etc. are in virtual machines, and the Mac itself will be cleaner. Doing this feels like operating a VPS.

怪我咯 · Answer

http://www.cnblogs.com/yjmyzz/p/run-mysq...
This post can solve your problem. There is an extra layer of Boot2Docker. The file used by the container is a virtual machine. file, the permissions are difficult to change

Cause of the problem:
This is a more complete answer in the comments, the views are more correct, for your reference
@mikeys Boot2Docker creates a VirtualBox share of /Users on your Mac to /Users on the Linux host. This is what lets you share any folder under your Mac's /Users directory with a docker container, because the paths are the same.

Really what it does is automatically mount a VirtualBox share named Users to /Users (under Linux), and it so happens that it creates a share called Users from your Mac's /Users.

The problem is that these shares are owned by the docker user (uid 1000) on in the Linux host. This means that any container that needs to write to a shared folder on your Mac will need to run its process as UID 1000 .

This is only a problem with Boot2Docker because it uses the virtual box sharing, which changes the uid of the share to the docker user and you can't change this easily from Linux.

In Vagrant, I usually solved this by changing my Vagrant file to use different permissions for the virtual box share:

config.vm.synced_folder ".", "/vagrant", :mount_options => ['dmode=777,fmode=666']
Maybe you could do something like that inside of your Boot2Docker image, I haven't looked into it. I think you would make these changes to /etc/rc.d/automount-shares in the Linux VM

One way I solved this was to just set my containers up so that I could configure them with the UID I wanted them to run their processes as, so I could just set it to 1000. The downside to this is that you basically need to create your own images for everything since most containers I've found don't let you do this.

I hope this helps.

怪我咯 · Answer

Sorry, I just saw it recently. I will give it a try and hope it can help you!

docker - 没有没有谁在MacOS+Toolbox下部署mysql并且成功挂载volume的？

reply all(4)I'll reply