this post was submitted on 13 Jul 2023
0 points (NaN% liked)

Voyager

5607 readers
60 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! ๐Ÿ‘‡

Number of sponsors badge

๐Ÿ’™

founded 1 year ago
MODERATORS
 

I am trying to build the Docker container for Voyager on my Raspberry Pi, and I'm facing some issues in the docker build process. It always falls apart at the corepack step after about 8-10 seconds. Interestingly, if I disable BuildKit, the build completes successfully, and the resulting image works perfectly fine. (I'm using it now.) However, disabling BuildKit leaves a message that eventually the old build method will be removed from the code.

I'm not entirely convinced it's a Voyager-specific error, or if it's something more appropriate for docker forums.

Docker CE version 24.0.4 on latest Raspbian 11 release.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 0 points 1 year ago (1 children)
[โ€“] [email protected] 1 points 1 year ago

By the way, since I did the one build with IPv6 disabled, I've since re-enabled it, and subsequent builds seem to accept that corepack is cached and haven't had further issues. Should it come up again, I'm going to have tcpdump running in the background just to see whether there is some host that the build process is trying to lookup that is returning bogus AAAA responses. (More often than not IPv6 problems stem from improper configuration either on the client or server side.)