By Morgan Lucas (she/her)
Under construction!
Docker Images are like a video game; Everything you need to play is in a neat little package and you can share it.
<aside> 💡
Well, 90s video games when you didn’t need to connect to the internet for updates.
</aside>
Different packages have different repositories.
I’m making a container to hold a redis database (redisDB)! Or, another one. I’ve done this before.
If the image I want isn’t local, Docker will pull it.
I make another container with a click counter and link it to the redisDB
Their services don’t quite correlate (A click counter and a database?), so I delete them.
I use docker network prune to remove a network no container is using. Possible to code an Ansible playbook to do similar for a Cisco machine, but it’s nice to have it built in.
Need to see what container is attached to what network interface? docker inspect [cont-name]