Error in starting the Enigma Docker Network

I get this error in runing docker network :
core_1 | error[E0432]: unresolved import core::hint
core_1 | --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/spin-0.5.0/src/once.rs:49:11
core_1 | |
core_1 | 49 | use core::hint::unreachable_unchecked as unreachable;
core_1 | | ^^^^ Could not find hint in core
core_1 |
core_1 | error[E0658]: const fn is unstable (see issue #24111)
core_1 | --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/spin-0.5.0/src/mutex.rs:109:5
core_1 | |
core_1 | 109 | / pub const fn new(user_data: T) -> Mutex
core_1 | 110 | | {
core_1 | 111 | | Mutex
core_1 | 112 | | {
core_1 | … |
core_1 | 115 | | }
core_1 | 116 | | }
core_1 | | |^
core_1 | |
core_1 | = help: add #![feature(const_fn)] to the crate attributes to enable
core_1 |
core_1 | error[E0658]: const fn is unstable (see issue #24111)
core_1 | --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/spin-0.5.0/src/rw_lock.rs:96:5
core_1 | |
core_1 | 96 | / pub const fn new(user_data: T) -> RwLock
core_1 | 97 | | {
core_1 | 98 | | RwLock
core_1 | 99 | | {
core_1 | … |
core_1 | 102 | | }
core_1 | 103 | | }
core_1 | | |
^
core_1 | |
core_1 | = help: add #![feature(const_fn)] to the crate attributes to enable
core_1 |
core_1 | error[E0658]: const fn is unstable (see issue #24111)
core_1 | --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/spin-0.5.0/src/once.rs:59:5
core_1 | |
core_1 | 59 | / pub const fn new() -> Once {
core_1 | 60 | | Self::INIT
core_1 | 61 | | }
core_1 | | |_____^
core_1 | |
core_1 | = help: add #![feature(const_fn)] to the crate attributes to enable
core_1 |
core_1 | error: aborting due to 4 previous errors
core_1 |
core_1 | Some errors occurred: E0432, E0658.
core_1 | For more information about an error, try rustc --explain E0432.
core_1 | error: Could not compile spin.
core_1 | warning: build failed, waiting for other jobs to finish…
core_1 | error: build failed
`
and then the EnigmaSurface always waiting for EnigmaCore .

1 Like

Same problem here. I’m expecting it behave the same in every single environment because it’s a docker container. Now it lookd like some dependencies have changed so it didn’t work as expected. I will watch this case close.

Same issue. Anyone can help?

This docker-network is being deprecated, and we will release a new version for Discovery in a matter of days. We are going to archive this repo very soon, so we will not be troubleshooting it anymore.

2 Likes

:joy::joy:you guys really should archive it sooner… I’ve been working on this for some time

The new beta developer release is out. Refer to this forum post.

The previous Docker release mentioned above has been deprecated and archived.

1 Like