ESP32 Firmware Development with Docker Sandboxes
docker.com
docker.com
We're using Rust with embassy on the esp platform and its quite wonderful.
We have all peripheral modules isolated and have non-peripheral modules compatible with an embassy desktop scheduler and mock peripherals.
Harnesses are good enough now that you can get them in a loop with the actual hardware.
The next step is to hookup a Saleae and have the agent test against actual signals.
Combining a dedicated small machine with a USB hub that supports per-port power cycling lets the agent iterate and un-wedge stuff with no human intervention for very long (days) periods. Obviously any software produced that way is unusable, but it’s incredible for debugging. Agent gets a programmable oscilloscope, power-cycling, and peripherals (also power-cycleable) emulating the various things our product talks to in the wild.
TL;DR I found the docker layers just caused confusion for the agent and giving her an old laptop was way simpler and much more powerful
I can just turn it off. I can unplug it from the network if I'm worried. I can easily isolate it network-wise using just a VLAN and normal firewalls. Hardware connectivity (ESP32 stuff I'm doing this weekend) -- as you describe -- is just easier.
- can someone with expertise in docker tell me why this guy is using isolate on top of docker to run untrusted user code? https://github.com/engineer-man/piston/blob/master/api/src/j...
1. A laptop with the development environment (DOS or Windows) kept in a box to use for updates / fixes
2. A VM on a NAS to use when a firmware in maintenance needs a fix
With more embedded tooling available on Linux, a docker image becames a natural choice.
Do better.
Everything happened for the first time sometime.
I'll do something much better, I'll stop feeding you with attention.
Also: