This message was deleted.

Hm... Poking in the code it looks like /etc/ always needs to be writable (at least during startup)

You’ll also need somewhere writable for the k3s db as well- under /var/lib/rancher/k3s/db if I recall. If you just need consistent state on boot, this could be tmpfs combined with a script to populate / copy the db into place before k3s starts. I’m sure there will be many more things to think about, too - like certificate rotation.

Yeah /var/lib is a tmpfs overlay in my tests at the moment, but probably needs to go to some persistent filesystem in the end.

https://github.com/k3s-io/k3s/issues/1683 - not a lot of info here but maybe useful

Ah... Writes to /usr too... Thanks for the pointer @bulky-computer-31499! Maybe I will just overlay everything for k3s...

I’d be interested in a summary of how you get this going!

Feel free to watch https://linaro.atlassian.net/browse/ORKO-65 😛. But I may resort to dirty hacks for some first version...