You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe
Charlie mocked up an initial flow for launching a disk image in #752, but that's just one aspect of what we'll need.
Describe the solution you'd like
We need a design or mockup for working with virtual machines: how you launch them from the disk image, what the UI to interact with them should look like, how to see the status, stop, or get back to a VM if you leave it running, etc.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Design complete. Short term, we've updated the disk images to have a Details page similar to most tables in Podman Desktop (#856). This gives us a place to put both build logs and VMs (#813) in a bit more of a consistent and organized way.
When using bootc there are really three artifacts that you interact with:
Bootable container images (a filtered set of container images)
Disk images
VMs
For (1), there's a request to have a separate page within this extension that just shows bootable images: #862. This page would be almost identical to the page in Podman Desktop, but the list would be filtered to only bootable containers and relevant actions, so that they're easier to find when you're focussed on bootc. Adding this page will require us to have sub-navigation similar to Kubernetes. (and possibly a point where we'd want a new intro homepage?)
For (2), we're now well served.
For (3), we do not have VM management yet - i.e. you will be able to start a VM, but we will not allow you to create multiple VMs, jump between them, etc. When this function does come (likely via podman-bootc) we would likely move VM launching to its own nav & page (no longer a tab within a disk image).
And finally, we blur 'building a disk image' (1->2) and 'existing disk images' (2) today. Building a disk image is a background task - ideally you'd kick off a build and see progress, have a way to jump back to the task, and the disk image wouldn't exist until the build is complete. At some point it will likely make sense to improve what we're doing here, but it makes sense to wait and see how PD task management evolves until we change anything.
Is your enhancement related to a problem? Please describe
Charlie mocked up an initial flow for launching a disk image in #752, but that's just one aspect of what we'll need.
Describe the solution you'd like
We need a design or mockup for working with virtual machines: how you launch them from the disk image, what the UI to interact with them should look like, how to see the status, stop, or get back to a VM if you leave it running, etc.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: