Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can't install the systemd-resolved with abroot pkg apply #396

Open
Vildnex opened this issue Feb 25, 2025 · 7 comments
Open

I can't install the systemd-resolved with abroot pkg apply #396

Vildnex opened this issue Feb 25, 2025 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@Vildnex
Copy link

Vildnex commented Feb 25, 2025

Config:

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

    "registry": "ghcr.io",
    "registryService": "registry.ghcr.io",
    "registryAPIVersion": "v2",
    
    "name": "vanilla-os/nvidia-exp",
    
    "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"
}

The package I am trying to install systemd-resolved by doing:

 abroot pkg add systemd-resolved
 abroot pkg apply

But When I am to apply the package I will get this error message every time:

⬢ [apx-vso-pico] ❯ abroot pkg apply
STEP 1/4: FROM localhost/abroot-293e6750-140b-4a8c-888d-be2a7b70cb39:latest
STEP 2/4: LABEL maintainer='Generated by ABRoot'
STEP 3/4: LABEL ABRoot.root=vos-a
STEP 4/4: RUN lpkg --unlock && apt-get install -y systemd-resolved && lpkg --lock
[INFO  netavark::firewall] Using iptables firewall driver
[INFO  netavark::network::netlink] Adding route (dest: 0.0.0.0/0 ,gw: 10.88.0.1, metric 100)
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libnss-resolve
The following NEW packages will be installed:
  libnss-resolve systemd-resolved
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 490 kB of archives.
After this operation, 1208 kB of additional disk space will be used.
Err:1 https://repo2.vanillaos.org sid/main amd64 systemd-resolved amd64 257.2-1
  404  Not Found [IP: 104.21.112.1 443]
Err:2 https://repo2.vanillaos.org sid/main amd64 libnss-resolve amd64 257.2-1
  404  Not Found [IP: 104.21.112.1 443]
E: Failed to fetch https://repo2.vanillaos.org/pool/main/s/systemd/systemd-resolved_257.2-1_amd64.deb  404  Not Found [IP: 104.21.112.1 443]
E: Failed to fetch https://repo2.vanillaos.org/pool/main/s/systemd/libnss-resolve_257.2-1_amd64.deb  404  Not Found [IP: 104.21.112.1 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
[INFO  netavark::firewall] Using iptables firewall driver
[INFO  netavark::network::bridge] removing bridge podman0
  ERROR   Apply command failed: building at STEP "RUN lpkg --unlock && apt-get install -y systemd-resolved && lpkg --lock": while running runtime: exit status 100
Error: building at STEP "RUN lpkg --unlock && apt-get install -y systemd-resolved && lpkg --lock": while running runtime: exit status 100
Usage:
  abroot pkg add|remove|list|apply [flags]

Examples:
abroot pkg add <pkg>

Flags:
  -d, --dry-run                       perform a dry run of the operation
  -f, --force-enable-user-agreement   force enable user agreement, for embedded systems
  -h, --help                          help for pkg

Global Flags:
  -V, --verbose   show more detailed output

  ERROR   building at STEP "RUN lpkg --unlock && apt-get install -y systemd-resolved && lpkg --lock": while running runtime: exit status 100

Even if the package was add properly:

abroot pkg add systemd-resolved
 INFO  Package(s) systemd-resolved added.
@kbdharun
Copy link
Member

Hi, sorry for the inconvenience, we are currently performing a maintenance with our repositories to update our stable images so ABRoot pkg functionality might not work as expected until later today/tomorrow as announced in our server.

Image

@kbdharun kbdharun self-assigned this Feb 25, 2025
@kbdharun kbdharun added the bug Something isn't working label Feb 25, 2025
@Vildnex
Copy link
Author

Vildnex commented Feb 25, 2025

All right, thanks for letting me know :D. In this case, I will test it again tomorrow and close this issue if everything works fine.

@kbdharun
Copy link
Member

kbdharun commented Feb 26, 2025

Hi, the maintenance has been completed and our stable images have been updated to a newer version (checkout https://vanillaos.org/updates to know more). ABRoot pkg functionality will now work as intended so I am closing this issue, feel free to reopen the issue if you still experience it.

@Vildnex
Copy link
Author

Vildnex commented Feb 26, 2025

@kbdharun Ok so... If this is finished it should work maybe I'm doing something wrong, but I get the exact same error as above.

More then that, if I will be to upgrade this via abroot upgrade before trying to install this package I will have this issue again Vanilla-OS/nvidia-image#61.

Am I doing something wrong?

@kbdharun kbdharun reopened this Feb 26, 2025
@kbdharun
Copy link
Member

kbdharun commented Feb 26, 2025

@kbdharun Ok so... If this is finished it should work maybe I'm doing something wrong, but I get the exact same error as above.

This time it could be due to outdated repo (while there is a way to update the host repo, it isn't ideal since image update will overwrite it), so the best approach would be to update the image first then apply the package change. But this is probematic:

More then that, if I will be to upgrade this via abroot upgrade before trying to install this package I will have this issue again Vanilla-OS/nvidia-image#61.

Am I doing something wrong?

This issue was reported in our server, and seems like we are missing kernel headers in our pinned kernel (causing issue with dkms in custom images and also breaking nvidia image, I will try to address this issue asap after discussing with the team).

Will update you here after the fix is pushed then you can update host and add back the package.

@Vildnex
Copy link
Author

Vildnex commented Feb 26, 2025

Thanks for the help and explication :D. I'm waiting for updates in this case :)

@kbdharun
Copy link
Member

Hi, the issue has been fixed now (and the nvidia image has been tested by the team). You can now update the image then after reboot apply the package change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants