Reboot fails with "certificate signed by unknown authority"

[pwFoo]

Because of some problems and a full disk I cleaned up (system-)docker of BurmillaOS (2.0 / latest) with the following commands.

[system-]docker system prune --all --volumes

I expected to delete all unused images, but during next reboot OS stopped working with errors to pull images from production.cloudflare.docker.com.

Is it Docker Hub, BurmillaOS or mybe network / cloudflare related?
Any chance to get it booting up again? Maybe with preloaded images?

@olljanat Hey, any hint how to fix that to be able to boot and login?

[olljanat]

To you get to console at all currently? Wget command mentioned in https://github.com/burmilla/os/releases/tag/v2.0.1 most likely helps if you do.

If not then options are trying with recovery mode or chroot with boot disk.

[pwFoo]

No console ready.
I running with 2.0 without that fix because 2.0 is shown as latest. There should be pushed an fix release.

Recovery is without network / nics. Need to setup network (if drivers available) to try it. Thanks

[pwFoo]

Sure that should work with .rancher ending?

sudo wget -O /etc/ssl/certs/ca-certificates.crt.rancher https://raw.githubusercontent.com/burmilla/os-initrd-base/master/assets/ca-certificates.crt

Removed it to got it working / booting up.

Don't know why... Looks like console image was deleted by prune / cleanup (system-)docker system...

Thanks! Haven't looked at the release page... You should push it as bug fix release 2.0.1 to be visible / available to ros os ...?

[olljanat]

Sure that should work with .rancher ending?

Good point. Looks that it is mapped to that inside of console so you need remove that extension if modifying in chroot

os/os-config.tpl.yml

Line 67 in afce4f9

- /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt.rancher

Thanks! Haven't looked at the release page...

#176 was open quite long time to make that everyone notices it. Reopened now as clearly everyone hasn’t yet updated to 2.0.1 / 2.0.2.

You should push it as bug fix release 2.0.1 to be visible / available to ros os ...?

That would be hard to accomplish because we would first need add support for it to ros command and then wait that everyone updates to version which have that support.