Docker incantations

 I find docker a bit obscure so I will list a short list of commands here to jog my memory.

Build the docker container:

docker compose up 

or

docker-compose up

See what docker containers are running to get their IDs

docker ps -a

Login to a container using bash: (while running):

docker exec -it d762049858c7 bash

See what the password/s are including for mysql for a docker container:

docker inspect d762049858c7 | grep -i password

Nuke the container to edit it to rebuild:

docker compose down

Copy a local file to a running container:

docker cp /path/to/local/file d762049858c7:/path/inside/container/

See what is going on:

docker logs d762049858c7

Get the container IP address:

docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' d762049858c7


Popular posts from this blog

throttle traffic on apache

sudo apt install apache2-utils sudo apt install libapache2-mod-evasive vi /etc/apache2/mods-enabled/evasive.conf service apache restart edit it and set values as per below or whatever else you like, the time quantities are seconds     DOSSiteInterval     1     DOSBlockingPeriod   10     #DOSLogDir           "/var/lock/mod_evasive"
Read more

Pause a program which is using too much CPU

Sometimes your battery is running low and you need to pause a program without quitting it or force-quitting it, so that you can preserve battery but not lose the job that the program is doing. To do this,  Step 1. open a terminal Step 2. type:  ps ax | grep -i  "<program name>" so for example, if it's photoshop you need to pause, replace "<program name>" with "photoshop" Step 3. Next to the results on the far left you'll see a number, usually with 5 digits. E.g. 12345. Step 4. Type:  kill -STOP 12345 where 12345 are the numbers obtained in Step 2-3. Step 5. When you want to resume the program, type kill -CONT 12345 It should then continue to operate or run as usual without problems.
Read more

/var/log/journal taking up lots of space

 If /var/log/journal is taking up too much space, you can clear it and prevent it growing too big again. Prevention: vi /etc/systemd/journald.conf   Look for: SystemMaxUse=2000M Or similar, and set it to a lower value Then: service systemd-journald restart Clearing once-off: journalctl --vacuum-time=2d assuming for example you want to clear everything before two days ago.
Read more