Check docker-compose version to see if it is higher than minimum required version

[muthusleuths]

If using an old version of docker compose everything looks normal during initial start up and after a while the blockchain container throws the following error which looks confusing.

stacks-blockchain      | Dumping core for pid 1
stacks-blockchain      | INFO [1675110289.046981] [testnet/stacks-node/src/main.rs:82] [main] stacks-node 2.05.0.6.0 (master:a71871a, release build, linux [x86_64])
stacks-blockchain      | INFO [1675110289.046997] [testnet/stacks-node/src/main.rs:140] [main] Loading config at path /src/stacks-blockchain/Config.toml
stacks-blockchain      | INFO [1675110289.049009] [testnet/stacks-node/src/event_dispatcher.rs:963] [main] Registering event observer at: stacks-blockchain-api:3700
stacks-blockchain      | ERRO [1675110289.066828] [src/chainstate/coordinator/mod.rs:927] [main] Sortition DB at /root/stacks-blockchain/data/xenon/burnchain/sortition does not support epoch 2.0
stacks-blockchain      | WARN [1675110289.066842] [src/chainstate/coordinator/mod.rs:965] [main] Unable to migrate chainstate DBs to the latest schemas in the current epoch
stacks-blockchain      | ERRO [1675110289.066846] [testnet/stacks-node/src/run_loop/neon.rs:364] [main] FATAL: chainstate database(s) are not compatible with the current system epoch
stacks-blockchain      | ERRO [1675110289.066851] [testnet/stacks-node/src/main.rs:58] [main] Process abort due to thread panic: panicked at 'explicit panic', testnet/stacks-node/src/run_loop/neon.rs:367:17
stacks-blockchain      | ERRO [1675110289.112777] [testnet/stacks-node/src/main.rs:60] [main] Panic backtrace:    0: stacks_node::main::{{closure}}
stacks-blockchain      |              at src/testnet/stacks-node/src/main.rs:59:18
stacks-blockchain      |    1: std::panicking::rust_panic_with_hook
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:702:17
stacks-blockchain      |    2: std::panicking::begin_panic_handler::{{closure}}
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:586:13
stacks-blockchain      |    3: std::sys_common::backtrace::__rust_end_short_backtrace
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:138:18
stacks-blockchain      |    4: rust_begin_unwind
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:584:5
stacks-blockchain      |    5: core::panicking::panic_fmt
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:142:14
stacks-blockchain      |    6: core::panicking::panic
stacks-blockchain      |              at rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:48:5
stacks-blockchain      |    7: stacks_node::run_loop::neon::RunLoop::instantiate_burnchain_state
stacks-blockchain      |              at src/testnet/stacks-node/src/run_loop/neon.rs:367:17

It would be ideal to have a error message to indicate that the user is in a unsupported version of docker-compose

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed. Please reopen if needed.