Closed
Description
At least on the containers-storage
transport, it seems that bootc install
absolutely requires a network connection due to it checking the remote instead of checking local storage first.
Here is an example:
$ bootc --version
bootc 1.1.6
# heres my containers-storage
$ sudo podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/ublue-os/bluefin beta 43f35a4d4153 46 hours ago 7.55 GB
# no network connection, running bootc install on the host directly
$ sudo bootc install to-disk --source-imgref=containers-storage:ghcr.io/ublue-os/bluefin:beta /dev/vda --filesystem btrfs --wipe
ERROR Installing to disk: Verifying fetch: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: pinging container registry ghcr.io: Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: Temporary failure in name resolution
# whenever i connect to a wifi or something, it just works
$ sudo bootc install to-disk --source-imgref=containers-storage:ghcr.io/ublue-os/bluefin:beta /dev/vda --filesystem btrfs --wipe
Installing image: docker://ghcr.io/ublue-os/bluefin:beta
Wiping /dev/vda1
Wiping device /dev/vda1
/dev/vda1: 8 bytes were erased at offset 0x00000052 (vfat): 46 41 54 33 32 20 20 20
/dev/vda1: 1 byte was erased at offset 0x00000000 (vfat): eb
/dev/vda1: 2 bytes were erased at offset 0x000001fe (vfat): 55 aa
Wiping /dev/vda2
Wiping device /dev/vda2
/dev/vda2: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef
Wiping /dev/vda3
# [...]
I am testing this from a beta Bluefin live ISO, but this environment shouldnt be any different than running this directly on any host system. Here is the ISO if anyone wants to test this directly where I am also testing it: https://download.projectbluefin.io/bluefin-live-stable.iso
Metadata
Metadata
Assignees
Labels
No labels