Open AlecRust opened 3 years ago
Hi, I have the same issue here, and in my case there is not even a difference between the usage of docker compose
or docker-compose
. Did you find any solution to fix this?
Last time I ran a project using this was a few months ago, and I think I just used docker-compose
which worked at the time. Sounds like maybe Docker has changed since then.
FYI: I don't have owner privileges to this repo, but this project is going to probably need a new regular maintainer because I don't use wordpress (or this project) in my day to day job anymore.
I'm open to grant owner privileges to whoever is willing to take over. It might need to move out of the visiblevc organization too though.
It still works on my macos machine. Only having this issue on my Windows 10 x64 machine. Is there someone else who can test/recreate this problem on a Windows machine?
The
wordpress-starter
documentation states to usedocker-compose
command to start i.e.When this command is run though Docker gives this notice:
If I switch to using
docker compose
based on this i.e.Then I get a different style of output when it's running, and
wordpress-starter
throws an error and exits:In my
docker-compose.yml
my wordpress service is already configured as-per the first example (with SYS_ADMIN etc.).Does
wordpress-starter
not support the newdocker compose
overdocker-compose
?