Configurator requires compose v1 or --compatibility option

[iay]

Feedback

I'm using Docker Desktop v4.22.0 under macOS. This version of Desktop ships with Compose v2, which by default creates container names like workshop-mattermost-1. The configurator expects the Mattermost container to be called workshop_mattermost_1, which is what Compose v1 used to do.

The result of this is that the configurator fails while trying to initialise the Mattermost container (and is continuously restarted). Mattermost displays a registration page rather than the login page, and it's not possible to log in.

Suggested Improvement

Ideally, the configurator should work with either container naming scheme.

A workround is to use the docker compose --compatibility option when bringing the stack up. This causes Compose v2 to operate in a compatibility mode in which the old container and volume naming conventions are used.

See https://stackoverflow.com/questions/69464001/docker-compose-container-name-use-dash-instead-of-underscore

Lesson Progress

• Lesson 01 completed or in-progress
• Lesson 02 completed or in-progress
• Lesson 03 completed or in-progress
• Lesson 04 completed or in-progress
• Lesson 05 completed or in-progress
• Lesson 06 completed or in-progress
• Lesson 07 completed or in-progress
• Lesson 08 completed or in-progress
• Lesson 09 completed or in-progress
• Lesson 10 completed or in-progress
• Lesson 11 completed or in-progress
• Lesson 12 completed or in-progress
• Lesson 13 completed or in-progress
• Lesson 14 completed or in-progress
• Lesson 15 completed or in-progress
• Lesson 16 completed or in-progress

[murasaki718]

I just submitted a fix that helped me - > #154