![使用docker(在OS X上的vagrant内部)获取“无法创建/写入文件‘/var/lib/mysql/is_writable’”](https://linux22.com/image/683294/%E4%BD%BF%E7%94%A8docker(%E5%9C%A8OS%20X%E4%B8%8A%E7%9A%84vagrant%E5%86%85%E9%83%A8)%E8%8E%B7%E5%8F%96%E2%80%9C%E6%97%A0%E6%B3%95%E5%88%9B%E5%BB%BA%2F%E5%86%99%E5%85%A5%E6%96%87%E4%BB%B6%E2%80%98%2Fvar%2Flib%2Fmysql%2Fis_writable%E2%80%99%E2%80%9D.png)
我正在尝试在 OS X 上托管的 vagrant 机器中使用 docker-compose/docker。运行“docker-compose up”总是失败,
mysqld:无法创建/写入文件“/var/lib/mysql/is_writable”(错误代码:13 - 权限被拒绝)
不过,我可以手动创建文件。(使用touch
和sudo -g vagrant touch
)
有人知道在哪里可以调试这个吗?
日志:
db_1 | Initializing database
db_1 | mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
db_1 | 2016-05-21T22:55:38.877522Z 0 [ERROR] --initialize specified but the data directory exists and is not writable. Aborting.
db_1 | 2016-05-21T22:55:38.877799Z 0 [ERROR] Aborting
我的docker-compose.yaml:
version: '2' services: db:
privileged: true
image: mysql
volumes:
- "./.data/db:/var/lib/mysql"
restart: always
environment:
MYSQL_ROOT_PASSWORD: wordpress
MYSQL_DATABASE: wordpress
MYSQL_USER: wordpress
MYSQL_PASSWORD: wordpress
我的Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "ubuntu/trusty64"
# config.vm.box = "debian/jessie64"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# sudo apt-get update
# sudo apt-get install -y apache2
# SHELL
#####################################################################
# Custom Configuration
config.vm.define "dev" do |dev|
# if File.directory?("~/Dev")
# dev.vm.synced_folder "~/Dev", "/vagrant/Dev"
# end
# custom: above does not work for symlinks
dev.vm.synced_folder "~/Dev", "/home/vagrant/Dev"
# dev.vm.synced_folder "~/Dev/docker", "/docker"
dev.vm.provider "virtualbox" do |vb|
vb.gui = false
vb.memory = "2048"
end
dev.vm.provision "shell",
run: "always",
inline: <<-SHELL
pushd /vagrant/conf
chmod 755 setup.sh && ./setup.sh
popd
SHELL
dev.ssh.forward_x11 = true
# Install the caching plugin if you want to take advantage of the cache
# $ vagrant plugin install vagrant-cachier
if Vagrant.has_plugin?("vagrant-cachier")
# Configure cached packages to be shared between instances of the same base box.
# More info on http://fgrehm.viewdocs.io/vagrant-cachier/usage
config.cache.scope = :machine
end
end
end
答案1
你能确认你的docker版本吗?
我遇到了同样的错误,但在更新到最新版本后它开始正常工作。
我现在正在运行:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
希望这对解决您的问题有帮助。