Docker image prune removes jupyter image

[hampusnasstrom]

It seems like the recommended docker image prune -a removes also the latest pulled jupyter image. It could be because I don't have it in the docker-compose file but rather pulled it separately. Or is this command meant to be run before you pull the new images?

[DanielYang59]

I also noticed this behaviour (also considering jupyter image is quite large), and I guess it's because docker compose up doesn't start a container for jupyter directly so it would be considered "unused".

Or is this command meant to be run before you pull the new images?

I usually use it as a manual garbage collection because docker is quite conservative in this end, so I don't think it's meant to run everytime before pull.

---

I guess we could have added a tag like:

  # jupyterlab image: (this is only used to pull the image, no service is run for this)
  jupyterlab_image:
    image: ghcr.io/fairmat-nfdi/nomad-distro-template/jupyter:main
    platform: linux/amd64
    container_name: nomad_jupyter_image
    pull_policy: always
    entrypoint: ["true"]
+   labels:
+     keeps: "true"
    deploy:
      replicas: 0 # Ensures the service isn't started

and then filter it with docker image prune -a --filter "label!=keep=true", not sure if it's worth it though @blueraft