Skip to content

Can't start with custom packages configured if DNS is broken #1001

@vilhalmer

Description

@vilhalmer

At startup when it tries to install custom packages, it will bail out if it can't reach the repo:

…
s6-rc: info: service init-docker successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-ssh successfully started
s6-rc: info: service init-user: starting
WARNING: updating and opening https://dl-cdn.alpinelinux.org/alpine/v3.23/main/aarch64/APKINDEX.tar.gz: DNS: transient error (try again later)
WARNING: updating and opening https://dl-cdn.alpinelinux.org/alpine/v3.23/community/aarch64/APKINDEX.tar.gz: DNS: transient error (try again later)
2 unavailable, 0 stale; 253 distinct packages available
[21:17:18] FATAL: Failed updating Alpine packages repository indexes
s6-rc: warning: unable to start service init-user: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
…

Removing all your custom packages works around the issue.

If this is due to DNS or other network configuration issues, this prevents ssh access to the HA host which makes debugging such issues more difficult. It seems like it would be preferable to continue startup without custom packages in this scenario, perhaps showing a warning at the prompt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions