Vanilla-OS / ABRoot

ABRoot is a utility that provides full immutability and atomicity to a Linux system, by transacting between two root filesystems. Updates are performed using OCI images, to ensure that the system is always in a consistent state.
http://abroot.vanillaos.org/
GNU General Public License v3.0
309 stars 24 forks source link

Unable to upgrade: building at STEP "RUN true": setup network: netavark (exit code 1): No such file or directory #345

Closed Babilinx closed 2 months ago

Babilinx commented 2 months ago

When trying to update manually from abroot upgrade, I get the following:

...
[files downloading]
6d9700aa9d8e [0/39 kB]       ■■■■■■■■■■■■■■■■■■■■■■■■■ 100% 
STEP 1/5: FROM ghcr.io/vanilla-os/desktop@sha256:3cf0e5928a4c66f08d02bf97387e89c2a96d3eecd607ac40f03966d78b35d2be
STEP 2/5: LABEL ABRoot.root=vos-a
STEP 3/5: LABEL ABRoot.BaseImageDigest=sha256:3cf0e5928a4c66f08d02bf97387e89c2a96d3eecd607ac40f03966d78b35d2be
STEP 4/5: LABEL maintainer='Generated by ABRoot'
STEP 5/5: RUN true
[INFO  netavark::firewall] Using iptables firewall driver
error running container: did not get container start message from parent: EOF
  ERROR   building at STEP "RUN true": setup network: netavark (exit code 1): No such file or directory (os error 2)
Error: building at STEP "RUN true": setup network: netavark (exit code 1): No such file or directory (os error 2)
Usage:
  abroot upgrade [flags]

Examples:
abroot upgrade

Flags:
  -c, --check-only   vérifie les mises à jour mais ne les applique pas
  -d, --dry-run      effectuer un lancement à sec de l'opération
  -f, --force        forcer la mise à jour même si le système est à jour
  -h, --help         help for upgrade

Global Flags:
  -V, --verbose   afficher une sortie plus détaillée

  ERROR   building at STEP "RUN true": setup network: netavark (exit code 1): No such file or directory (os error 2)

From what I can see, it seems that some files are never downloaded (0% of DL but the proces continue on other files).

ABRoot config file:

{
    "autoRepair": true,
    "maxParallelDownloads": 2,

    "registry": "ghcr.io",
    "registryService": "registry.ghcr.io",
    "registryAPIVersion": "v2",
    "name": "vanilla-os/desktop",
    "tag": "main",

    "iPkgMngPre": "lpkg --unlock",
    "iPkgMngPost": "lpkg --lock",
    "iPkgMngAdd": "apt-get install -y",
    "iPkgMngRm": "apt-get remove -y --autoremove",
    "iPkgMngApi": "https://packages.vanillaos.org/api/pkg/{packageName}",
    "iPkgMngStatus": 2,

    "differURL": "https://differ.vanillaos.org",

    "partLabelVar": "vos-var",
    "partLabelA": "vos-a",
    "partLabelB": "vos-b",
    "partLabelBoot": "vos-boot",
    "partLabelEfi": "vos-efi",

    "libPathStates": "/var/lib/abroot/states",
  "PartCryptVar": "/dev/mapper/vos--var-var",
  "thinProvisioning": true,
    "thinInitVolume": "vos-init"
}

ABRoot version: v2.0.1

Note that I'm trying to get back to default desktop image from a custom desktop image. It is also doing the same thing in a VM (still using my own image) and when trying to update the custom image.

I may be dumb and have done a breaking change in my image but I prefer posting an issue as it may be an other issue.

axtloss commented 2 months ago

Related to https://github.com/Vanilla-OS/core-image/issues/73 but it shouldn't happen in the main branch, only development

Babilinx commented 2 months ago

Verbose output.

This time it fail sooner. output-verbose.log

Babilinx commented 2 months ago

Related to Vanilla-OS/core-image#73 but it shouldn't happen in the main branch, only development

You know what? I'm using dev core image :joy: (i'm dumb...)

Seriously, is there an actual fix that you are aware of?

axtloss commented 2 months ago

nope, you'd have to switch back to the main image though i guess that's not really possible if abroot is broken.. maybe check in the other root?

Babilinx commented 2 months ago

I'll try that. Thanks!

Edit: Closed as is it tracked elsewere

kbdharun commented 2 months ago

nope, you'd have to switch back to the main image though i guess that's not really possible if abroot is broken.. maybe check in the other root?

Even if ABRoot is broken it is possible to do this to still upgrade the system (instructions from Tau):

In rare cases where ABRoot has a fatal bug it might be necessary to use the newest version.

Note that this should only be used if other troubleshooting steps didn't work since the new ABRoot version is not guaranteed to work with your system.

Open a Terminal, run:

host-shell pkexec
cd /tmp
wget https://github.com/Vanilla-OS/ABRoot/releases/latest/download/abrootv2.tar.gz
tar -xvf abrootv2.tar.gz
/tmp/abrootv2 upgrade