I have a DJI osmo nano camera and I just saw an error log on the sd card that makes it pretty clear the OS for the camera runs in a docker container on the camera.
it's sort of useless info, and I'm guessing they do that to make the process of updating easier where they just ship a new container image.
@jerry still wild that Docker runs on a camera
@deepthoughts10 not just any camera, but one that records in 4k and is the size of my thumb
@jerry @deepthoughts10 giving very 'when all you have is a hammer' vibes
@airshipper @jerry @deepthoughts10 I saw some guy was messing with the telemetry on his DJI drone and ended up Master of 7k DJI roombas because they all share the same default creds or protocol or something. There might be someone out there right now trying to get Jerry's camera to suck dirt.
The DJI Romo robovac had security so poor, this man remotely accessed thousands of them

A man discovered that thousands of DJI Romo robot vacuums had a security issue that could have let strangers look into owners’ homes and remotely control them.

The Verge
@jerry still can't do kernel-updates. The other reply where there were two partitions taking turns sounds easier in that regard. You can still have other partitions for data and use a VM to test on dev-setups… but I may just be old-school already
@jerry that fixes the "it works on my camera" issue.
@Andres I imagine it solves or make easier a lot of problems, like updates
@jerry easier rollbacks πŸ€”
@Andres @jerry Over here we make two partitions on the eMMC device and download a full filesystem image (including kernel) onto the "other" one for updates. Switching back to the previous version can be done in an instant.
@mansr @Andres @jerry there's some interesting stuff happening in this space. Yocto and bootc come to mind
@jerry
Are you sure it wasn't talking about the other kind of "image"?