We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was working on a recreation scenario for #503 and tried a number of things.
colima start junk --vm-type=qemu --mount-type="" was accepted, but shouldn't a valid mountType be required?
colima start junk --vm-type=qemu --mount-type=""
It results in mountType: "" and
mountType: ""
$ colima status -p junk INFO[0000] colima [profile=junk] is running using QEMU INFO[0000] arch: aarch64 INFO[0000] runtime: docker INFO[0000] socket: unix:https:///Users/rfay/.colima/junk/docker.sock
(Note that the mountType is not reported there)
But the mountType ends up being 9p, so 9p seems to be the default still on 0.5.2?
But... Unable to recreate the problem described here using this technique.
I was even able to do
colima start j2 --mount-type="xxx" --vm-type=qemu
colima start j3 --mount-type="xxx" --vm-type=xxx
I recommend validation on each of those arguments (and all of the rest as well).
I note that manually changing colima.yaml with mountType: yyy and vmType: yyy also results in no validation on start.
mountType: yyy
vmType: yyy
colima status -p j3 shows
colima status -p j3
$ colima status -p j3 INFO[0000] colima [profile=j3] is running using QEMU INFO[0000] arch: aarch64 INFO[0000] runtime: docker INFO[0000] mountType: yyy INFO[0000] socket: unix:https:///Users/rfay/.colima/j3/docker.sock
Apparently it decides QEMU is the thing to do, but it thinks that mountType is yyy.
yyy
Colima Version: 0.5.2 Lima Version: 0.14.2 Qemu Version: 7.2.0
colima status
described above
Failure for unsupported vm type or mount type
No response
The text was updated successfully, but these errors were encountered:
Basic validation of config, fixes abiosoft#548
a56a131
fe625fb
No branches or pull requests
Description
I was working on a recreation scenario for #503 and tried a number of things.
colima start junk --vm-type=qemu --mount-type=""
was accepted, but shouldn't a valid mountType be required?It results in
mountType: ""
and(Note that the mountType is not reported there)
But the mountType ends up being 9p, so 9p seems to be the default still on 0.5.2?
But... Unable to recreate the problem described here using this technique.
I was even able to do
colima start j2 --mount-type="xxx" --vm-type=qemu
with no complaint from colimacolima start j3 --mount-type="xxx" --vm-type=xxx
I recommend validation on each of those arguments (and all of the rest as well).
I note that manually changing colima.yaml with
mountType: yyy
andvmType: yyy
also results in no validation on start.colima status -p j3
showsApparently it decides QEMU is the thing to do, but it thinks that mountType is
yyy
.Version
Colima Version: 0.5.2
Lima Version: 0.14.2
Qemu Version: 7.2.0
Operating System
Output of
colima status
Reproduction Steps
described above
Expected behaviour
Failure for unsupported vm type or mount type
Additional context
No response
The text was updated successfully, but these errors were encountered: