Open vortex-hue opened 9 months ago
From Docker Compose docs:
Effective July 2023, Compose V1 stopped receiving updates and is no longer in new Docker Desktop releases. Compose V2 has replaced it and is now integrated into all current Docker Desktop versions. For more information, see Migrate to Compose V2.
Does it make sense to include compatibility with an EOL product when the new version under active development is already supported?
Sure, I thinking both in support is best, cause some containers are on v1 while others built upon V2 tech, leaving v1 totally out of sync because it has stopped receiving updates would seem like abandoning Ubuntu 20.0.4 LTS because new versions are out, i believe both should be supported
On Fri, 26 Jan 2024, 20:06 Andrea Falco, @.***> wrote:
From Docker Compose docs https://docs.docker.com/compose/:
Effective July 2023, Compose V1 stopped receiving updates and is no longer in new Docker Desktop releases. Compose V2 has replaced it and is now integrated into all current Docker Desktop versions. For more information, see Migrate to Compose V2 https://docs.docker.com/compose/migrate.
Does it make sense to include compatibility with an EOL product when the new version under development is already supported?
— Reply to this email directly, view it on GitHub https://github.com/kaleidos-ventures/taiga-docker/pull/124#issuecomment-1912552149, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXYCBIAFCBBG45EEPRIXEXDYQP5BZAVCNFSM6AAAAABCH7FXF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGU2TEMJUHE . You are receiving this because you authored the thread.Message ID: @.***>
I had issues while running taiga with Docker Compose because the most stable version is v1.x and the docker commands are for v2.x, so i created extra files to support v2.x and also v1.x so that others can run theirs smoothly, Further questions are welcome.