Straightforward question:
If I use docker-compose up -d everything works fine and I get Mediawiki running on my localhost and my bash works fine.
If I use docker-compose up I get this: https://pastebin.com/FL8u9iHv and my bash freezes there. This got me curious. What am I lacking/doing wrong, if anything?
So -d means detach and put it in the background.
I am not that familar with docker-compose so this may be wrong, but what i think is happening: since you dont detach you see debug info which would normally be hidden. Your terminal is attached to the apache process. Since apache does not take input (since it normally runs in the background) it simply ignores anything you press on the keyboard. Thus it looks like things are frozen, where really its not frozen its just apache ignores input on stdin and doesn't normally output anything.
Thank you! That's what is happening because it literally ignores everything beside Ctrl+C to exit gracefully. Do I have anything to really debug though? I mean, for Apache.
Probably not. Generally if you wanted to access the container, you would want to start a new /bin/sh process and connect to that.
