bug: bonfire minio/mc eqalpha/keydb can't start

[la02w]

What happened?

revolt_events_1

la02@la02:~/docker/revolt$ docker logs revolt_events_1
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

revolt_createbuckets_1

la02@la02:~/docker/revolt$ docker logs revolt_createbuckets_1
Added `minio` successfully.
The cluster is ready
mc: <ERROR> Unable to make bucket `minio/attachments`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/avatars`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/backgrounds`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/icons`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/banners`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/emojis`. Your previous request to create the named bucket succeeded and you already own it.

revolt_redis_1 did not generate any logs

la02@la02:~/docker/revolt$ docker logs revolt_redis_1
la02@la02:~/docker/revolt$