-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot boot VM with writableStoreOverlay
+ shares
#43
Comments
Apologies, I only tested this feature with volumes. Do they work for you? Alternatively, is there anything we could do about it in our custom stage-1? I will update the docs to reflect the current situation. |
Yes, volumes work fine with the I might have another go at it later, but for now
|
So I looked at my old notes where I encountered the issue before and did some testing based on other similar/reported issues with Some suggestions pointed to using
I have tried with quite a few combinations of Thinking about it I cannot actually see a use case where we would need a full writable share instead of a volume, so if it is too complex it may be not be worth supporting, at least volumes will fit my use case for development machines. |
I am unable to use a writable store when using shares, the documentation states that the path at
microvm.writableStoreOverlay
must be writable, and #20 mentions that this should work with a writabe overlay on share.I can get a writable store using
microvm.volumes
, i.e.however trying to use a share instead with something like:
results in a VM which does not boot, stating that the upper fs is missing required features.
This was tested with
cloud-hypervisor
specifically.I couldn't find a test or example which shows this usecase, is this meant to be supported or am I doing something wrong?
The text was updated successfully, but these errors were encountered: