Skip to content

Docker Build: Update xbps error #633

Description

@CodeMan99

Environment

Use of the ghcr.io/void-linux/void-glibc:20250601R1 container image.

Description

When using this image, the docker build fails as the xbps system requires an upgrade.

If there is documentation on how to handle this case, I haven't found it. Links are appreciated.

Dockerfile

# syntax=docker.io/docker/dockerfile:1

ARG VOID_CIMPL=glibc
ARG VOID_TAGNAME=20250601R1
FROM ghcr.io/void-linux/void-${VOID_CIMPL}:${VOID_TAGNAME}

RUN xbps-install --sync --memory-sync --yes bind

COPY ./etc.named/named.conf /etc/named/named.conf
COPY ./var.named/team.bytezone.dev.zone /var/named/team.bytezone.dev.zone

ENTRYPOINT [ "/usr/sbin/named", "-g", "-u", "root" ]
EXPOSE 53/tcp

Docker Build Error

$ docker compose build
... <snip>
 => ERROR [named 2/4] RUN xbps-install --sync --memory-sync --yes bind                                                                                                                                     3.9s
------
 > [named 2/4] RUN xbps-install --sync --memory-sync --yes bind:
0.951 [*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
0.951 x86_64-repodata: [2024KB 0%] 74MB/s ETA: 00m00s
1.385 x86_64-repodata: [2024KB 7%] 331KB/s ETA: 00m13s
2.285 x86_64-repodata: [2024KB 69%] 1055KB/s ETA: 00m00s
2.578 x86_64-repodata: 2024KB [avg rate: 1517KB/s]
3.884 The 'xbps' package must be updated, please run `xbps-install -u xbps`
------
failed to solve: process "/bin/sh -c xbps-install --sync --memory-sync --yes bind" did not complete successfully: exit code: 16

Activity

  1. classabbyamp commented on Jun 16, 2025

    @classabbyamp
    Member

    this is how xbps currently works, though it might change in #597

    you should xbps-install -Suy xbps && xbps-isntall -uy to ensure xbps and the container environment are up-to-date

    also, --sync negates --memory-sync, you don't need both.

  2. CodeMan99 commented on Jun 16, 2025

    @CodeMan99
    Author

    Ah. Well, I hope this does become a warning. I really like using VOID for containers and I have grown tired of long incantations just to install a single package.

    Thank you.

  3. classabbyamp commented on Jun 16, 2025

    @classabbyamp
    Member

    I've updated the base container to avoid this for now

  4. CodeMan99 commented on Jun 16, 2025

    @CodeMan99
    Author

    I consider my issue resolved. Feel free to close if there is not anything else to track here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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