hey @bupd !

While trying Harbor CLI via the Docker-based setup, I noticed a small first-run UX issue around config mounts.
In README.md, the container example mounts the config file directly:

-v $HOME/.config/harbor-cli/config.yaml:/root/.config/harbor-cli/config.yamlOn a clean system, ~/.config/harbor-cli/ doesn’t exist, so Docker fails on first run with a file/directory mount error.
After the directory exists, the command works, which makes this confusing for new users.

I also noticed CONTRIBUTING.md uses:

-v $HOME/.harbor/config.yaml:/root/.harbor/config.yaml. This often works because ~/.harbor/ already exists, but it’s still fragile for true first-run setups. So README and CONTRIBUTING behave differently.

Suggested improvement (docs-only):

Mount the config directory, not the file:- v $HOME/.config/harbor-cli:/root/.config/harbor-cli. Align README + CONTRIBUTING.md to the same patternUpdate the alias example to avoid file mounts. This avoids Docker file/directory conflicts and makes first-run behavior reliable.

Happy to open an issue / PR if this sounds reasonable ! open for your views/suggestions