Docker is probably nice to use, but it’s UI is just so goddamn auful for something that other people think everyone is instantly able to pick up. The massive disconnect between containers, images, instances, or whatever near-synonym that the UI expects you to know, and what they actually do is astounding.
I still have ZERO goddamn idea which port is internal or external in the -p80:80 option because every single fucking guide just has it there and expects you to just magically know which one is what and EVERY LAST ONE just uses the same internal and external port. And good fucking luck looking it up and getting even vaguely relevant results (I’ve tried)
So when something says “oh just use docker-compose …” I groan because I have not one fucking idea what actually happens. Does that create a container? Or an image? Or instance? Which one of those is the template and which one of those is the running code which is identified by a completely meaningless hexadecimal string?
Also how do I back them up? Do I also have to back up EVERYTHING in the container? What if I just want to back up the database? How would I pass through a folder on an external drive? Or do I have to duplicate the hundreds of gigabytes of photos I have for just this container? Are those included in backups if backups are even a thing? What if I can’t store all that on my boot drive? Am I able to move JUST that single container or image or whatever the fuck?
There’s a reason I like running things on bare metal. It’s plenty secure if it’s just for you and also behind additional authentication and put it in its own user like I do. It just fucking works.
okay hear me out: what if you took the time to learn it and learn how it works. literally all of your gripes are solvable one way or another. your ignorance fuels your hatred.
For me
Why?
Docker is probably nice to use, but it’s UI is just so goddamn auful for something that other people think everyone is instantly able to pick up. The massive disconnect between containers, images, instances, or whatever near-synonym that the UI expects you to know, and what they actually do is astounding.
I still have ZERO goddamn idea which port is internal or external in the
-p 80:80option because every single fucking guide just has it there and expects you to just magically know which one is what and EVERY LAST ONE just uses the same internal and external port. And good fucking luck looking it up and getting even vaguely relevant results (I’ve tried)So when something says “oh just use docker-compose …” I groan because I have not one fucking idea what actually happens. Does that create a container? Or an image? Or instance? Which one of those is the template and which one of those is the running code which is identified by a completely meaningless hexadecimal string?
Also how do I back them up? Do I also have to back up EVERYTHING in the container? What if I just want to back up the database? How would I pass through a folder on an external drive? Or do I have to duplicate the hundreds of gigabytes of photos I have for just this container? Are those included in backups if backups are even a thing? What if I can’t store all that on my boot drive? Am I able to move JUST that single container or image or whatever the fuck?
There’s a reason I like running things on bare metal. It’s plenty secure if it’s just for you and also behind additional authentication and put it in its own user like I do. It just fucking works.
okay hear me out: what if you took the time to learn it and learn how it works. literally all of your gripes are solvable one way or another. your ignorance fuels your hatred.
Okay. Any good guide?
tywele has a great answer, also; sorry for such an abrasive response, wasn’t in a great mood 😅
Its fine.
This helped me greatly in understanding all the different things about Docker/Docker Compose: https://gabrieltanner.org/blog/docker-compose/
I also struggled with the external/internal port thing etc