devilbox: 403 forbidden after update
after update (from git & containers incl. removing and recreating images) from 0.13 to 0.14 I get an 403 on all hosts (including localhost). also ssl cert is not correct set up now (security page). Can anyone confirm or a hand for debugging?
-
[ x] Pull latest dockers (e.g.:
docker pull cytopia/<used_docker>) before runningdocker-compose updone that -
[ x] Specify used docker versions (php, web and database) php 7.0, 7.1, 7.1 database mariadb-10.1 apache 2.2 2.4
-
[ x] Attach logs for php, mysql and webserver (found in
log/directory) the log files did not update. this is the compose up output -
[x ] Start with debug mode and attach docker-compose output (
.envsettingDEBUG_COMPOSE_ENTRYPOINT=1) logs.txt -
[x ] Never use different mysql|mariadb versions on the same
HOST_PATH_MYSQL_DATADIRon existing database files. Different mysql|mariadb versions might upgrade/corrupt existing database files. If you have done that already, start with a different path ofHOST_PATH_MYSQL_DATADIR(to an empty directory) and try again.
Please also specify the following info:
- [x ] Which operating system are you at (Linux, OSX or Windows) windows 10
- [x ]
docker versiondocker ce Version 18.03.1-ce-win65 (17513) - [x ]
docker-compose version1.21.1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 39 (18 by maintainers)
Commits related to this issue
- Fix #288 by documenting some edge cases — committed to cytopia/devilbox by cytopia 6 years ago
Yes, basically, when you asked me to try the new commit, I tried it and the issue was still there. I still had empty folder when I shelled in and did an ls.
I then went reading through the forum posts you had pointed out previously which discussed some of the problems that a lot of us have when initially setting up Docker for Windows, in that we cannot get it to share our drives. It took me nearly a week of reading numerous trouble tickets, forum threads, and blog posts and trying many procedures to get my c: drive shared with Docker, to begin with before I even got to install and run Devilbox.
While reading this section I was looking at different settings to make sure they had not changed and I noticed that a couple of my drives were not displayed. That seemed odd, so I decided to try resetting my Windows credentials with Docker, and the drives showed up, but c: was no longer shared, none of them were shared. so I reset and reshared my c: drive, then fired up my Devilbox and it worked exactly as expected.
I’m not sure where or what to tell the Docker people. I know it may not be fair to you, but my only interest in Docker is in it powering my Devilbox. I understand very, very little about it, and everything I have done with it has been according to the instructions in the Devilbox manual.
I am very much NOT a server guy, I just want a local server that I can know as little as possible about to work on WordPress themes and plugins locally and push my work out through GIT. I’m doing it with Devilbox because so far it’s the most approachable way to do this for me with an actual Linux environment that closely approximates the servers I run the real sites on.