#Perhaps a problem of cache after having updated some Python scripts of my Dagger project...

1 messages · Page 1 of 1 (latest)

zealous marten
#

I'm using WSL2, building my own Docker image, creating a container and jump in an interactive shell (docker in docker enabled and working)

I can play with Dagger like running dagger call --help, dagger call version, etc. i.e. functions I've created.

I'm also working in a devcontainer so I can update my Python functions (like doing some code refactoring). My codebase is shared with my Docker container.

At some time, dagger call --help didn't work anymore and I got strange errors coming from, I think, Docker (screenshot attached).

It seems it's something related to any cache mechanism because I just need to exit my container and run docker compose down --remove-orphans --rmi all --volumes then rebuild the image, create the container again and jump in the container. And now, the previously failed dagger call --help runs as expected.

For info ...