Scott Wallace

Ensure you have the `EMULATOR_ARGS` environment variable set. e.g. ``` -e EMULATOR_ARGS=-camera-back webcam0 ```

I got this and worked out it was because the environment variable `https_proxy` was set. Try unsetting that and see what happens.

I've looked into this and have come up with a hypothesis: the test suite is being built ahead of time and each test is populated with an instance of `httpclient.get_http(...)`...

We could clear the pool, as I've done above, for a short-term solution whilst thinking about a better long-term solution. My initial thoughts are to utilise a shared HTTP pool...

Okay but previously `latest` had all three architectures and this is a departure from what was done previously. One might argue that there should be a `stable` tag or, perhaps,...

A couple of years on and this is still an issue.

I'm having the same issue and adding this extra argument stops the container from restarting but I'm wondering why it's happening in the first place.

I've noticed that after the warning happens, though, the bridge stops responding. I've reverted the change but the bridge crashes regularly, after the ping timeout. The container restarts, some messages...

I'm also seeing this but with a standard bridge network. ```yaml networks: traefik: internal: true name: traefik_internal ipam: config: - subnet: 10.0.3.0/24 ```

Works for me on GrapheneOS.