Getting “Can't create/write to file '/var/lib/mysql/is_writable'” using docker (inside vagrant on OS X)MySQL Can't Create/Write To FileSSH'ing into Windows VirtualBox with VagrantVagrant bridge to openvpn interface?Unable to build_image when using Docker provisioner on vagrantnpm install on vagrant virtualboxCoreOS-vagrant: How to mount /var/lib/docker from hostNew Vagrant Packaged Windows Server 2016 returning Authentication failure. RetryingVagrant xenial64 NFS synced dir 'preserve permissions' failure on bcrypt buildDockerise a laravel application - getting permission denied on apache servervagrant shared folder on windows 10 with winnfsd became very slow
Chain rule instead of product rule
Why favour the standard WP loop over iterating over (new WP_Query())->get_posts()?
How do we explain the use of a software on a math paper?
Why is python script running in background consuming 100 % CPU?
What's is the easiest way to purchase a stock and hold it
Was Tyrion always a poor strategist?
Running server on home network with HTTPS
Who is frowning in the sentence "Daisy looked at Tom frowning"?
Addressing an email
Parse a C++14 integer literal
Vehemently against code formatting
Managing heat dissipation in a magic wand
Is there any official Lore on Keraptis the Wizard, apart from what is in White Plume Mountain?
Why does the U.S military use mercenaries?
Is it possible to view all the attribute data in QGIS
Bookshelves: the intruder
Why could the Lunar Ascent Engine be used only once?
How to convince boss to spend notice period on documentation instead of new projects
FIFO data structure in pure C
How to safely discharge oneself
Should I twist DC power and ground wires from a power supply?
Have I found a major security issue with login
What were the "pills" that were added to solid waste in Apollo 7?
Why does string strummed with finger sound different from the one strummed with pick?
Getting “Can't create/write to file '/var/lib/mysql/is_writable'” using docker (inside vagrant on OS X)
MySQL Can't Create/Write To FileSSH'ing into Windows VirtualBox with VagrantVagrant bridge to openvpn interface?Unable to build_image when using Docker provisioner on vagrantnpm install on vagrant virtualboxCoreOS-vagrant: How to mount /var/lib/docker from hostNew Vagrant Packaged Windows Server 2016 returning Authentication failure. RetryingVagrant xenial64 NFS synced dir 'preserve permissions' failure on bcrypt buildDockerise a laravel application - getting permission denied on apache servervagrant shared folder on windows 10 with winnfsd became very slow
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am trying to use docker-compose/docker inside a vagrant machine hosted on OS X. Running 'docker-compose up' always fails with
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
I can manually create the file just fine, however. (Using touch
and sudo -g vagrant touch
)
Does anyone know where to look to debug this?
Log:
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
My 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
My 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
mysql mac-osx docker vagrant docker-compose
add a comment |
I am trying to use docker-compose/docker inside a vagrant machine hosted on OS X. Running 'docker-compose up' always fails with
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
I can manually create the file just fine, however. (Using touch
and sudo -g vagrant touch
)
Does anyone know where to look to debug this?
Log:
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
My 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
My 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
mysql mac-osx docker vagrant docker-compose
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44
add a comment |
I am trying to use docker-compose/docker inside a vagrant machine hosted on OS X. Running 'docker-compose up' always fails with
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
I can manually create the file just fine, however. (Using touch
and sudo -g vagrant touch
)
Does anyone know where to look to debug this?
Log:
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
My 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
My 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
mysql mac-osx docker vagrant docker-compose
I am trying to use docker-compose/docker inside a vagrant machine hosted on OS X. Running 'docker-compose up' always fails with
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
I can manually create the file just fine, however. (Using touch
and sudo -g vagrant touch
)
Does anyone know where to look to debug this?
Log:
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
My 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
My 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
mysql mac-osx docker vagrant docker-compose
mysql mac-osx docker vagrant docker-compose
asked May 21 '16 at 22:58
nielsbotnielsbot
163118
163118
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44
add a comment |
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44
add a comment |
1 Answer
1
active
oldest
votes
Can you confirm your docker version?
I was getting the same error, but after I updated to the latest version it started to work.
I am now running:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
Hope this helps with your problem.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f778259%2fgetting-cant-create-write-to-file-var-lib-mysql-is-writable-using-docker%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Can you confirm your docker version?
I was getting the same error, but after I updated to the latest version it started to work.
I am now running:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
Hope this helps with your problem.
add a comment |
Can you confirm your docker version?
I was getting the same error, but after I updated to the latest version it started to work.
I am now running:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
Hope this helps with your problem.
add a comment |
Can you confirm your docker version?
I was getting the same error, but after I updated to the latest version it started to work.
I am now running:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
Hope this helps with your problem.
Can you confirm your docker version?
I was getting the same error, but after I updated to the latest version it started to work.
I am now running:
$ docker --version
Docker version 1.12.0-rc2, build 906eacd, experimental
$ docker-compose --version
docker-compose version 1.8.0-rc1, build 9bf6bc6
Hope this helps with your problem.
answered Jun 21 '16 at 23:37
Bernardo SilvaBernardo Silva
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f778259%2fgetting-cant-create-write-to-file-var-lib-mysql-is-writable-using-docker%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm not using vagrant, but I get exactly the same issue on my mac. Did you get anywhere with this?
– yurasuka
May 26 '16 at 14:25
by the way - I removed the volumes section and it works (for my purposes). I assume you got that yml from docs.docker.com/compose/wordpress ?
– yurasuka
May 26 '16 at 14:44