Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Compose project name not set #14

Open
kc9jud opened this issue Mar 18, 2022 · 3 comments
Open

Docker Compose project name not set #14

kc9jud opened this issue Mar 18, 2022 · 3 comments

Comments

@kc9jud
Copy link

kc9jud commented Mar 18, 2022

Docker Compose defaults to the basename of the project directory if no project name is set. Here, that means the project is simply called docker. This shows up in, for example, the output of docker compose ls and the name of the networks created. This should be set to bitwarden instead.

kc9jud added a commit to kc9jud/self-host that referenced this issue Mar 18, 2022
@joseph-flinn
Copy link
Contributor

See comment on #15

@kc9jud
Copy link
Author

kc9jud commented Apr 11, 2022

I think this is still not fixed, despite the problems with #15. At minimum, Bitwarden should not be creating networks with names like docker_default.

@joseph-flinn joseph-flinn reopened this Apr 11, 2022
@vipergts450
Copy link

I think this is still not fixed, despite the problems with #15. At minimum, Bitwarden should not be creating networks with names like docker_default.

I was also confounded by this when attempting a self-hosted install initially, but was able to work around it by creating a "docker-compose.override.yml" file in ./bwdata/docker which contains:

version: '3'

networks:
  default:
    name: bitwarden_internal
  public:
    name: bitwarden_public

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants