Skip to content

Anaconda install breaks when using customization options #458

@fenpaws

Description

@fenpaws

Using the anaconda-iso build type with customization leads to an ISO that is not able to launch the Anaconda.

I used various combinations of these customization options, from only using the ISO one to the modules; nothing worked. The only time Anaconda launches with customizations is with the following one.

[customizations.installer.kickstart]
contents = ""

The error i get when booting:

darcut-initqueue: timeout, still watiting for following initqueue hooks:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ] "
/lib/dracut/hooks/initqueue/finished/kickstart.sh: "[ -e /tmp/ks.cfg.done ] "
dracut-initqueue: starting timeout script

How to reproduce:

[customizations.iso]
volume_id = "TEST OS"
application_id = "test-os"
publisher = "me"

[customizations.installer.kickstart]
contents = ""

[customizations.installer.modules]
enable = [
  "org.fedoraproject.Anaconda.Modules.Storage"
]
disable = [
  "org.fedoraproject.Anaconda.Modules.Network",
  "org.fedoraproject.Anaconda.Modules.Security",
  "org.fedoraproject.Anaconda.Modules.Services",
  "org.fedoraproject.Anaconda.Modules.Users",
  "org.fedoraproject.Anaconda.Modules.Subscription",
  "org.fedoraproject.Anaconda.Modules.Timezone"
]
sudo docker run \
    --rm \
    -it \
    --privileged \
    --pull=missing \
    --security-opt label=type:unconfined_t \
    -v ./iso.toml:/config.toml:ro \
    -v ./output:/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    quay.io/centos-bootc/bootc-image-builder:latest \
    --type anaconda-iso \
    --use-librepo=True \
    --verbose \
    ghcr.io/ublue-os/bluefin:lts-hwe

Metadata

Metadata

Assignees

Labels

🐞 bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions