Launching a VM image fail with default sizes
Bug #2076907 reported by
Simon Fels
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Anbox Cloud |
Fix Released
|
Medium
|
Simon Fels | ||
Bug Description
Trying to launch a VM image gives the following error
$ amc launch -r --vm jammy:android13
Error: Failed creating instance from image: Source image size (16106127360) exceeds specified volume size (15000010752)
Using a larger disk size
$ amc launch -r --vm jammy:android13
makes the instance start.
It looks like the underlying partition sizes of our VM images changed somehow.
| Changed in anbox-cloud: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 1.23.1 |
| Changed in anbox-cloud: | |
| milestone: | 1.23.1 → 1.23.2 |
| Changed in anbox-cloud: | |
| assignee: | nobody → Simon Fels (morphis) |
| status: | Triaged → In Progress |
| Changed in anbox-cloud: | |
| status: | In Progress → Fix Committed |
| Changed in anbox-cloud: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
