Issues with hbbr/s after docker compose build.

It doesn't seem like hbbr or hbbs are functioning correctly after building them in docker compose

I keep getting these logs:

hbbr:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

hbbs:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

thread 'flexi_logger-flusher' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/std/src/sys/pal/unix/time.rs:130:68:

called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }

I'm just following the docker compose guide. Not sure what else to do.

The only thing I did different was adding version: '3.1' at the top of the yml config. (It looks like the guide page needs to be updated)

Start with the Docker Compose guide linked in the issue and the compose configuration used for the build. Reproduce the hbbr and hbbs startup failure, then determine whether the guide or its compose example needs correction; done means the documented setup no longer produces the reported permission errors.