Theme dir already exists on image (re)build

[urshulgi]

First of all, thank you for this project, I was trying to install zsh on docker and found this very helpful.

The first time I built the image it worked well. When I tried to build my image again, the script fails because the directory already exists I guess. This is how I'm rebuilding it:

docker compose -f docker-compose.dev.yml up --build -d

And the error:

6.203 fatal: destination path '/root/.oh-my-zsh/custom/themes/powerlevel10k' already exists and is not an empty directory.
------
failed to solve: process "/bin/sh -c sh -c \"$(wget -O- https://github.com/deluan/zsh-in-docker/releases/download/v1.2.1/zsh-in-docker.sh)\"" did not complete successfully: exit code: 128

[Kopczynski]

@urshulgi Assuming this is a build cache issue with volumes on subsequent builds. I would highly recommend cleaning up volumes between builds

Ultimately you have a handful of options, You can force recreate just the container (which will reuse and preserve the original volume) and will likely not work if the root issue is the volume being preserved between builds.

docker compose -f docker-compose.dev.yml up --force-recreate -d

Or better yet, force re-bake the image before trying to run it:

docker compose -f docker-compose.dev.yml build --no-cache && docker compose -f docker-compose.dev.yml up -d

But I believe the hyper correct answer when using compose would be to actually clean up your composed resources (specifically volumes) before attempting to build again with something along the lines of:

docker compose -f docker-compose.dev.yml down -v && docker compose -f docker-compose.dev.yml up --build -d

If you are still having issues after trying the full clean rebuild, please share your docker-compose.dev.yml with the relevant service and Dockerfile. Remember to remove any sensitive data they may contain.