Marc Lennox

OK @majorz, I figured out what the issue is. In my wifi-connect Dockerfile, I've added `network-manager` to the list of installed packages, in order that I can use the `nmcli`...

FROM balenalib/%%BALENA_MACHINE_NAME%%-debian:latest On Thu, 23 Jan 2020 at 10:10, Zahari Petkov wrote: > Thanks, I will try that. Just to reassure - are you using the newer > balenalib images,...

Same result if I use FROM balenalib/%%RESIN_MACHINE_NAME%%-debian Works fine without `network-manager`, fails to bring up the captive portal with `network-manager` installed

Very strange. It is 100% reproduceable for me. I'm using a multi-container deployment for my testing. Will try with single container just in case. Is there a way I can...

Yep it does On Thu., Jan. 23, 2020, 12:39 Zahari Petkov, wrote: > For multi-container make sure it has privileged: true and network: host. > > — > You are...

Well, I now was able to reproduce the issue without having network-manager package installed. Rebooting the device then made it work properly. In looking at the logs, I see the...

Adding the following before calling `wifi-connect` seems to make the problem go away ``` nmcli connection down id "WiFi Connect" || true nmcli connection delete id "WiFi Connect" || true...

Correct. I think what also might exacerbate the problem in my particular setup, is that I use the `timeout` option, then (in a loop) restart wifi-connect. I have been able...

@meech-ward I've made the script a little more robust (dealing with a possible failure of each nmcli call), but yes, that's basically all I'm doing before launching wifi-connect, and it...

I get this also.