Self-hosted failure with broken docker-compose.yml

Ask the Community Password Manager
,
1

Anyone run into this? We’ve been self hosted for a while, just did an update to latest and:

ERROR: The Compose file '/home/bitwardenuser/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for networks: 'public'
Unsupported config option for services: 'web'
ERROR: The Compose file '/home/bitwardenuser/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for networks: 'default'
Unsupported config option for services: 'icons'

and it’s not even the same error on each startup attempt:

ERROR: The Compose file '/home/bitwardenuser/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for networks: 'default'
Unsupported config option for services: 'events'
ERROR: The Compose file '/home/bitwardenuser/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'mssql'
Unsupported config option for networks: 'public'
2

Hi @colohost,

your issue seems to have been previously reported here: 2024.4.2 update broke my docker-compose.yml · Issue #4078 · bitwarden/server · GitHub

It likely has to do with the removal of the version in the config and it defaulting to the older docker-compose.

I hope this helps and please add any new info to that ticket.

Kind regards,
Daniel