Closed jimbobbennett closed 2 years ago
@jimbobbennett thanks for reporting this issue. We are still tracking in our backlog root causing and fixing issue #467. To confirm that it is the same problem, could you try the workaround in #467 and let us know if that resolves the symptoms you are observing?
@marianan - I can't, the workaround is to roll back Docker to 2.1, but I am using Apple Silicon, and this isn't supported with that version.
@jimbobbennett I see, thanks for your response. In that case I am assuming that this is a different issue and I am filing it separately. It is in our backlog. We will update this thread with our findings.
@jimbobbennett in your scenario you are trying to get an IoT Edge device inside a docker container. While we work out the specific compatibility issues between Docker and Mac here, i am curious if any of these other tools can unblock your scenario:
Moving forward, we are no longer going to support this functionality, so I am closing this issue. For more details, please see https://github.com/Azure/iotedgedev/pull/525.
Steps to Reproduce:
Expected:
It should work
Actual:
The container gives an error and stops:
This is the same as #467, but reopening as it's still an issue.
@marianan - you asked on that issue to share the config.yaml. This cannot be accessed as the container stops with the given error.
@cindydeng1998 - you mention the Quickstart. I've tried this, but I get errors as it's an AMD64 container and I'm using an Apple Silicon Mac. When I run
iotedgedev init
it can't retrieve my connection string, then I get set faults: