I spent a week trying different configurations to solve this issue, the two main docker platforms I list below:
Windows 10 running linux docker container
Ubuntu 18.04 LTS running linux docker container
The final result on both platforms were consistent:
libwebsockets.h not found error
Mosquitto build fails
Not enough space available on the container
Workarounds (note: this works on a failed container):
Increase the default docker container size allocated by the docker daemon form 20Gb to 40Gb. I found the final build is 20.7Gb total and takes about 7 hours on Windows and 4 hours on Ubuntu...Give or take. This is done by modifying the docker daemon.json file.
docker attach <container ID> (note: CTRL-p CTRL-Q to SIGKILL)
Attach to the docker container and use VIM to modify the .config file and:
a. Search for all instances of the keyword "mosquitto" and comment them out from the build configuration. If you need mosquitto, you'll have to find another way around the issue.
note: I recommend addding the "is not used" value after commenting out the line
Either run make menuconfig to add libwebsockets library and the libwesockets examples to the build configuration. Or while you're modifying the .config file, do a search using VIM for libwebsockets and add the library and examples to the build.
note: I built libwebsockets library by [using an * in menuconfig or =y in .config they are accomplishing the same thing] and set the libwebsockets examples [M in menuconfig or =m in .config]
make -j1 V=s
Run make [options] inside of the attached container. Docker automatically creates several intermediate containers when necessary and I found that using a Dockerfile can be problematic for Cross-Compile build process.
Yes, I agree with you. This seems much more elegant.
I started wondering about their function while thinking whether it is possible to provide a fast interface between multiple Omegas. It seems this is not exactly what I was looking for but still a very powerful mechanism.
Pi Zero W is a loss leader. That part can someday disappear. I agree spec wise its better but Onion is much better when handling network tasks IMO. Dual WiFi, 5 Ethernet Ports, etc. It's also PCB board solderable. If the Pi Zero W was PCB board solderable I would of went with that part.
Thank you for the suggestion with the power supply.
This morning I have tried a number of different power supply units (including the official rPi3 plug and cable) and this allowed me to get the device setup and SD card expanded as per the guides.
Issue now is the wifi looses connection to my home internet? The AP is still up but the 'second connection' to the router fails?
If it helps, I use apple airport router and a number of AP. The wifi failed on both router/ap AND also failed when tethering to my mobile phone wifi hotspot?
Now if I boot the device up with the ethernet expansion board connected (I use the expansion dock with my Omega2+) I can get network address/connectivity from my router/network. But again, remove the ethernet module and I am back to only having the ability to SSH/WebConsole via the Omega AP.
Could this be power related?, The Omega is using the latest firmware available from the Onion repos and flashed using the onion guides.