Open russellhaering opened 1 year ago
Looking into this briefly. I would not have guessed that the first thing you could encounter would be our own port conflicts...but at least it fails fast? Never even attempts to touch an enclave :)
First enclave:
$ docker run \ -d \ --name enclave \ --device=/dev/nitro_enclaves:/dev/nitro_enclaves:rw \ -p 8001:8001 \ us-docker.pkg.dev/edgebit-containers/containers/no-fly-list:enclave-latest # running perfectly
Second enclave:
$ docker run \ --name enclave2 \ --device=/dev/nitro_enclaves:/dev/nitro_enclaves:rw \ -p 8002:8002 \ us-docker.pkg.dev/edgebit-containers/containers/no-fly-list:enclave-latest INFO enclaver::run > starting egress proxy on vsock port 17002 ERROR enclaver > error running enclave: Address in use (os error 98)
Looking into this briefly. I would not have guessed that the first thing you could encounter would be our own port conflicts...but at least it fails fast? Never even attempts to touch an enclave :)
First enclave:
Second enclave: