You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of (in addition to) org.opencontainers.image.vendor you might want to use your own label io.diveinto.docker.group="diveintoansible-lab" for example.
Thanks for your feedback and insight @sdavids - appreciated.
We use host volume mounts for persistence and the ability to edit files locally, that said though it's not used that often even though it's a feature.
I've been considering removing this and may switch to standard volumes. This is the only variable for me in this feedback, the rest of it are logical improvements.
I know it's not optimal, but since the only problems are the images and local volumes, you can cleanup like this, while the compose setup is running and you are in the lab root directory:
Hi,
please add a cleanup script to your repo.
After finishing the course one should be able to easily get rid of everything.
The easiest way would be to label all your images, volumes, and networks.
Open Container Initiative - Pre-Defined Annotation Keys
Dockerfile - LABEL
Compose file / Networks / labels
Compose file / Volumes / labels
Compose file / Services / labels
Dockerfile
docker-compose.yml
You currently use anonymous volumes, so you might want to convert them to named volumes with a label and/or you might want to update your README:
diveintoansible-lab/README.md
Line 191 in b9205df
⇒
docker compose rm / options
Instead of (in addition to)
org.opencontainers.image.vendor
you might want to use your own labelio.diveinto.docker.group="diveintoansible-lab"
for example.This is how the cleanup script could look like:
docker image prune - filtering
The text was updated successfully, but these errors were encountered: