How to use docker

ALWAYS REMOVE THE -D

It makes you not see why shit isn’t working

index

Not all files are optional

.env files are not equal to .gitignore files
While .gitignore serves no apparent purpose, .env makes the dockerization succed 1

docker ps -a

Displays a messy list of all your dockerized stuff, usefull when you need to delete

docker stop

stops misbehaving dockers from running so they can be deleted

docker start

If you want to start the dockerization again, just use docker start

docker rm

docker ps -a gives you a short hash, put that after rm and it deltes when dockerized stuff isn’t working.

Caution: Because of the messy list from ps -a its very easy to undockerize more than planned

docker prune volumes -a

Saves space after undockerizing things. I am not confident I remember the order of the fruit and the volume, if it doesn’t work, mix them up

docker compose up

Takes a dockerfile and dockerizes it and runs it 2

Missing commands:

  • Stop dockerized thing from running (if its running you cant delete it)
  • [ x] Set dockerized things free from its weird networking
  • Describe how to set up the seemingly misspelled named thing that lets you point domains at dockerized things3
  • Setting up several things that mayhaps be related in one dockerization
  • Document usefull minus letters
  • Check if docker start can be used with minus letters

Further research

  • Check if there is such a thing as: docker exec 4
    • Find the correct term for “sshing into a docker”

Containers with or without shells

If
a container has shells, I can interact with it
else
who knows

To be explored.

using git

Usage of git has been moved to git cheat sheet.

Usefull tips

  • Port 3000 is just some odd number all examples love to use as the port
  • the file that makes a dockerization usually needs a bunch fields changed5
  • sometimes you can forgo all the dealing with text files and just write something after docker and then program/prograM:WTF and it just sets you up without all the hassle 6

Footnotes

  1. Sometimes at least, the success rate is like installing photoshop in ReactOS

  2. Its unclear how to do this with more minus letters after

  3. In the broken dockerization file for saltcorn it is mentioned

  4. Claimed to give ssh access to dockerizations

  5. Mayhaps to make the process make sense, if there was nothing needing input, why bother with the convoluted process of dockerization

  6. Don’t be dissapointed if it doesn’t work, most dockerizations fail for the first 37 attempts. If it seems like a burden you can’t overcome, just do something else for a while, someone will probably make a better dockerization