I’ve been using Docker for a while now, and I’m exploring the possibilities of ResinOS for a future project.
I’ve just flashed an image after following the “getting started” on resin.io, and now I have a read-only filesystem flashed on my Raspberry Pi where I can’t setup neither my company proxy, neither my company nexus mirroring Docker nexus (both conf would be in systemd conf for docker daemon, files like /etc/systemd/system/docker.service.d/http_proxy.conf and /etc/systemd/system/docker.service.d/launch_options.conf).
Also, I’d need to add my company nexus certificate in /etc/docker/certs.d and modify /etc/ntp.conf a bit, so that would be 4 conf files.
So what would be the way to deal with this ? Do I need to create my own OS distribution just to setup 4 conf files ?
UPDATE : I have to say after reading the doc, I’ve found there is an “overlay” non read-only partition, so I’ve tried to copy /etc/hosts to /mnt/state/root-overlay/etc/hosts, but after modifying /mnt/state/root-overlay/etc/hosts by adding a host, I can’t ping it by his name, so I guess there is an additional step, or maybe I don’t understand how to configure a read-only rootfs.