Closed vinnyperella closed 5 months ago
Hi there!
Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/self-host/issues/222
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.
This issue will now be closed.
Thanks!
Hi there!
Thank you for your report, it seems like it is a duplicate of this one #222
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.
This issue will now be closed.
Thanks!
This is not a duplicate of https://github.com/bitwarden/self-host/issues/222 this is a completely different issue. It's complaining about the "version: '3'" parameter inside the docker-compose.yml file that's used to start Bitwarden. In the latest version of the docker compose binary the version parameter is deprecated.
I have to agree with @vinnyperella, this issue is not related to #222 I've manually commented out the version line in docker-compose.yml, and the warning is no longer given when starting bitwarden. It appears the current docker-compose.yml is not fully compatible with the latest docker compose version. Removing the version line makes it compatible.
@Greenderella could you please reopen this issue? It's not a high priority since it's just a warning but as I mentioned in my initial issue post it could cause some concern for people running Bitwarden self-hosted that are not aware of the reason for the warning. The solution should be to remove the version parameter from docker-compose.yml as @GrahamTolhurst mentioned the parameter is obsolete anyway.
Sorry, I misinterpreted the issue. This has been escalated for further investigation. If you have more information that can help us, please add it below.
Regards
This is low priority as it doesn't appear to cause any issues and is just a WARN but it might confuse people and make them think there's an issue. I updated my docker compose to v2.25.0 which is the latest version and when I ran "./bitwarden.sh stop" or "./bitwarden.sh start" I received the following warning.
WARN[0000] /opt/bitwarden/bwdata/docker/docker-compose.yml:
version
is obsoleteOne of the changes in docker compose v2.25.0 is to bump compose-go to v2.0.0.
https://github.com/docker/compose/releases https://github.com/docker/compose/pull/11623
And one of the changes for compose-go v2.0.0 is to "warn user version is obsolete".
https://github.com/compose-spec/compose-go/releases/tag/v2.0.0 https://github.com/compose-spec/compose-go/pull/575
From the above pull request.