Docker cant run image openwrtorg/rootfs:x86-64 about docker HOT 6 CLOSED

Can you please run uname -a in the docker container? I'm wondering if it is because the host system uses a different kernel than opkg excepts, but that's may be unrelated. I'll keep investigating

from docker.

Could it be that the rootfs snapshot of the docker image is too old for the current luci snapshot from downloads.openwrt.org?

I'm actually surprised that luci depends on the kernel package, but the error looks like the common version mismatch that happens when using older snapshots and installing newer packages.

A workaround is to use opkg --force-depends to ignore the dependency, but I guess the proper fix would be to rebuild the rootfs docker image regularly.

from docker.

but I guess the proper fix would be to rebuild the rootfs docker image regularly.

They're build every day at 4am via GitLab pipeline schedules. Currently it's broken as one of the tests for image builder is currently failing due to the x86/64 image generation refactoring ls: cannot access './bin/targets/x86/64/*combined-squashfs.img.gz': No such file or directory and we're simply not aware about it.

It's quite strange, that GitLab doesn't send out failure emails in case of scheduled pipeline failures like it does for ordinary pipelines after the git push pipeline runs.

from docker.

It's quite strange, that GitLab doesn't send out failure emails in case of scheduled pipeline failures like it does for ordinary after the git push pipeline runs.

Seems like this needs to be explicitly configured in https://gitlab.com/openwrt/docker/-/services/pipelines_email/edit

from docker.

GitHub automatically closed this issue by merging PR #50, please reopen if the issue is still existing...

from docker.

I've just tested it and the opkg install uhttpd luci-base luci-mod-admin-full luci-theme-bootstrap luci-i18n-base-en luci-i18n-firewall-en luci-i18n-base-fr luci-i18n-firewall-fr worked.

from docker.