this post was submitted on 13 Jul 2023
7 points (100.0% liked)

Voyager

5604 readers
29 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
[โ€“] ziddey@lemmy.world 2 points 1 year ago (3 children)
[โ€“] frosty@pawb.social 1 points 1 year ago* (last edited 1 year ago)

I do run IPv6, but not exclusively!

Tacking "strace" onto the front of the docker build command gives me a lot of nice output before step 1, but at the crucial step 3, there's nothing. However, I decided to temporarily disable IPv6 processing on the device, and lo and behold, it carries on without a problem.

That means either my IPv6 tunnelbroker or some of BuildKit's services are having issues handling IPv6 traffic. (I was gonna say it was corepack, but that's run even with BuildKit turned off.) Now to find a way to get the build to work with IPv6, but that's my homework now.

Thanks for the tip!

load more comments (2 replies)