I was rebuilding a Gimlet image with the following command:
ptime -m ./helios-build image \
-p helios-dev=https://pkg.oxide.computer/helios/2/dev/ \
-P "$proto" \
-B \
-F optever=0.36 \
-F ntp \
-N "$name" \
-o "$OSDIR/$image"
The image didn't end up working the way I expected, because it included a svc:/site/postboot service that conflicted with the definition of the one I layer in via the external proto area facility (-P).
It occurs to me that this service should not be included unless explicitly requested for bench Gimlet images, as it does things we do not want production sleds to do; e.g., importing a ZFS pool called "data" if one exists.
I was rebuilding a Gimlet image with the following command:
The image didn't end up working the way I expected, because it included a
svc:/site/postbootservice that conflicted with the definition of the one I layer in via the external proto area facility (-P).It occurs to me that this service should not be included unless explicitly requested for bench Gimlet images, as it does things we do not want production sleds to do; e.g., importing a ZFS pool called "data" if one exists.