I’ve recently installed 10updocker on my new Debian 12 distribution, but I’m encountering issues when trying to create new sites.
Initially, I attempted to create a site in the usual manner. However, 10updocker indicated that the wplocaldocker network did not exist. To resolve this, I manually created the network in Docker, using the same parameters that I found in the source files of 10updocker.
After this step, I tried once again to create a new website. This time, 10updocker indicated that the wplocaldockerCache volume did not exist. As with the network, I decided to manually create this volume.
Despite manually creating both the network and volume, I’m still experiencing issues. Specifically, I’m unable to create a new site due to an error message from 10updocker stating: “Error: ‘/var/www/html/’ is not writable by current user.”
To address this, I added both the current user and root to the Docker group. Unfortunately, this action did not seem to have any effect.
Does anyone have any suggestions on how to resolve these issues?
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Troubleshooting
Describe your question
I’ve recently installed 10updocker on my new Debian 12 distribution, but I’m encountering issues when trying to create new sites.
Initially, I attempted to create a site in the usual manner. However, 10updocker indicated that the wplocaldocker network did not exist. To resolve this, I manually created the network in Docker, using the same parameters that I found in the source files of 10updocker.
After this step, I tried once again to create a new website. This time, 10updocker indicated that the wplocaldockerCache volume did not exist. As with the network, I decided to manually create this volume.
Despite manually creating both the network and volume, I’m still experiencing issues. Specifically, I’m unable to create a new site due to an error message from 10updocker stating: “Error: ‘/var/www/html/’ is not writable by current user.”
To address this, I added both the current user and root to the Docker group. Unfortunately, this action did not seem to have any effect.
Does anyone have any suggestions on how to resolve these issues?
Code of Conduct