You can replace the OS on most Android devices.

Specifically- devices made by Google have been unlocked allowing replacement of the software.

You still have to put together a working kernel and drivers, environment, etc.

Not much stopping folks from doing that though.

GrapheneOS, Ubuntu, and others have made headway for some devices.

Each device potentially uses different hardware implementation and features.

Or, maybe writing firmware and code that doesn’t make money is the opposite of profit.

Where is the incentive to write code that reduces security and costs money they won’t recover ?

This is a crowdstrike issue specifically related to the falcon sensor. Happens to affect only windows hosts.

Redhat and Debian are separate projects, tmk.

This was a fast response, and doesn’t cover the whole scope of handling networking in docker. As mentioned elsewhere there is a different network philosophy for Standalone Containers & Overlay networking.

You declare the ip in your setup, or in the yaml file. An example for the docker-compose file is in the link below. I’d expect you’ll want to declare the network and such as well, if you’re not familiar.

https://gist.github.com/natcl/3d881d00a56c8a961e6dab8ba51a5a37