Following Docker’s philosophy of “one application per container” you should have a database container for each WordPress instance. This way each database is isolated from the others. Should anything happen to one database it will not affect the others. Also, if you want to migrate or take down one website you only need to act … Read more
Regarding the wp –info output, that makes sense. If you don’t have any packages installed (see wp package –help or a global configuration files (wp-cli.yml) then those items would be blank. You can run the wp command from any location. If you’re anywhere within your website’s folder structure it will automatically detect the site you’re … Read more
The problem, as the error description indicates, is permissions. Based on that tutorial, nginx is running under the www-data user, but WP folders are owned by deployer. If you change the ownership of your $WP_ROOT to www-data:www-data, you will find that you can update your WP. I’m not amazing at security, so there may be … Read more
You can replace image using custom values.yaml file. For example you can create values.yaml containg this content Documentation for all values, you can find in the README.md for that chart. This docs are generated directly from values.yaml file, so you can use directly the values.yaml file Then install it with helm: Volume override In the … Read more
You can replace image using custom values.yaml file. For example you can create values.yaml containg this content Documentation for all values, you can find in the README.md for that chart. This docs are generated directly from values.yaml file, so you can use directly the values.yaml file Then install it with helm: Volume override In the … Read more
After a bit of digging, the problem is with this line that I added in my config.php that removed the missing FTP error when I started the container: After that I tried many times to chown the directories of the site, with no success. Which is strange because I used the root account to change … Read more
It depends on your OS. Here are the few locations, with commands for few Operating Systems: Ubuntu (old using upstart ) – /var/log/upstart/docker.log Ubuntu (new using systemd ) – sudo journalctl -fu docker.service Amazon Linux AMI – /var/log/docker Boot2Docker – /var/log/docker.log Debian GNU/Linux – /var/log/daemon.log CentOS – /var/log/message | grep docker CoreOS – journalctl -u docker.service Fedora – journalctl -u docker.service Red Hat … Read more
Those documents are outdated. I’m guessing the 1.6 in the URL is for Docker 1.6, not Compose 1.6. Check out the correct syntax here: https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode. You are looking for network_mode when using the v2/v3 YAML format.
As of v 0.7.0 of the private registry you can do: and you will get a json payload: to give more background here is how I started my registry:
The centos dockerfile has a default command bash. That means, when run in background (-d), the shell exits immediately. Update 2017 More recent versions of docker authorize to run a container both in detached mode and in foreground mode (-t, -i or -it) In that case, you don’t need any additional command and this is … Read more