-
Notifications
You must be signed in to change notification settings - Fork 75
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
install: A few minor patches #549
Conversation
This can take substantial time. Signed-off-by: Colin Walters <walters@verbum.org>
We previously changed the rootfs `mkfs` invocation to be verbose; for consistency let's do the same for the EFI partition as well as the bootloader run just so people can see what's going on more. Signed-off-by: Colin Walters <walters@verbum.org>
It's the default. Signed-off-by: Colin Walters <walters@verbum.org>
I think we can ignore the failing tests here, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
"--device", | ||
device.as_str(), | ||
rootfs.as_str(), | ||
]); | ||
Task::new_and_run("Running bootupctl to install bootloader", "bootupctl", args) | ||
Task::new("Running bootupctl to install bootloader", "bootupctl") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I know @bcrochet ran into this before when I was shoulder surfing with him.
let imgstate = | ||
ostree_container::deploy::deploy(&sysroot, stateroot, &src_imageref, Some(options)).await?; | ||
println!("Deployment complete"); | ||
let imgstate = crate::utils::async_task_with_spinner( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I sanity checked this on my system, it was too fast to actually see the spinner but I verified it omits the Deployment complete
output and instead just puts out done
as expected. I'm assuming if the deployment was slower I would see the actual spinner 😄
On Tue, May 21, 2024, at 2:07 PM, John Eckersberg wrote:
👍 I sanity checked this on my system, it was too fast to actually see
the spinner but I verified it omits the `Deployment complete` output
and instead just puts out `done` as expected. I'm assuming if the
deployment was slower I would see the actual spinner 😄
If you're testing with podman-bootc you need
containers/podman-bootc#37
and its followup in containers/podman-bootc#41
to see the spinner.
|
install: Add a spinner for container deployment
This can take substantial time.
Signed-off-by: Colin Walters walters@verbum.org
install: Be verbose for EFI creation and bootloader install
We previously changed the rootfs
mkfs
invocation to beverbose; for consistency let's do the same for the EFI partition
as well as the bootloader run just so people can see
what's going on more.
Signed-off-by: Colin Walters walters@verbum.org
bootloader: Drop --src-root /
It's the default.
Signed-off-by: Colin Walters walters@verbum.org