On Sun, 2021-05-23 at 17:51 +0200, Johannes Kastl wrote:
I had to replace one of my nodes, and the replacement does not properly
No problem, mounting the rootfs from a rescue disk and chrooting and...
read-only? Somehow the overlay for /etc does not work from within a
And I seem not to find any documentation on the exact layout of the
subvolumes and the overlay. Is that simply not in the wiki (except the
(As the machine has a 32 character root password that ansible created
for me, I
thought using a rescue stick would be easier...
Sorry for the long reply, been a busy week.
My first thought before trying to answer this question is - 'Why?'
Typically speaking I would say that any MicroOS/Kubic node that has
issues should just be replaced and with combustion/ignition it should
be easy to reproducibly deploy fresh nodes for your clusters.
I'm not sure what you mean by the layout of the btrfs subvolumes..it is
in the wiki
it is only documenting the deviations from our defaults which are on
The overlay itself is more complex, as its meant to be solely managed
by transactional-update. But put simply, /etc maps to
/var/lib/overlay/$SNAPSHOTNUM/etc where $SNAPSNOTNUM is the snapshot
number currently in use.
This is also documented in the fstab
Does this help?
Linux Distribution Engineer - Future Technology Team
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer