[turborepo] Unable to build Alpine docker image with turbo@canary

[weyert]

What version of Turborepo are you using?

1.7.0@canary

What package manager are you using / does the bug impact?

npm

What operating system are you using?

Mac

Describe the Bug

I am trying to build a Alpine-based docker image with the latest canary version of turbo but it's failing with libc

Expected Behavior

Able to successfully build a Alpine-based docker image

To Reproduce

Run docker build -f ./Dockerfile . were the Dockerfile has the following contents:

# syntax = docker/dockerfile:1.2
FROM node:lts-alpine3.17 as installer


RUN mkdir -p /opt/app && chown node /opt/app && chgrp node /opt/app && mkdir -p /opt/app/patches && chown node /opt/app/patches && chgrp node /opt/app/patches

ENV NO_UPDATE_NOTIFIER=true

# Install the libc compatibility layer for Alpine
RUN apk add --no-cache tree libc6-compat ca-certificates && \
    update-ca-certificates
RUN apk update

# Install the most recent version of NPM v8
RUN npm install -g npm@8 turbo@canary

Reproduction Repo

No response

[tknickman]

@weyert thanks for reporting this.

Our ubuntu binaries require glibc now, but we should definitely support alpine, which means we'll need a new binary targeting musl (x86_64-unknown-linux-musl) I believe. I'll take a look into this

[weyert]

Yeah, I think in 1.6.3 you needed libc6-compat to make it work with Alpine but that approach doesn’t work with 1.7 anymore

when I replace turbo instead of turbo@canary the docker image build succeeds

[tknickman]

Yep, there's a short description of the general issue here #3039. But we're still chasing them all down as part of the move to Rust.

[weyert]

Do you think it is fixable? Love to try Turborepo 1.7 in Alpine on Gitlab CI without needing to switch distros

If I install gcompat via apk add gcompat then I am getting the following error during my docker build:

#14 12.43 npm ERR! Error: Command failed: /opt/app/node_modules/turbo/bin/turbo --version --skip-infer
#14 12.43 npm ERR! Error relocating /opt/app/node_modules/turbo/bin/turbo: __res_init: symbol not found

Looks like there were similar issues in the Next project: vercel/next.js#30713

[tknickman]

It should be yes, we've been looking into this one over the past day or so - we definitely want this to be supported out of the box with no (or minimal changes) needed in an alpine container.

[weyert]

This is still a problem for me. Any news @tknickman ?

[tknickman]

@weyert Yep! This will be fixed in the next canary (not yet released). This one took a bit to track down and figure out a suitable approach to a fix - so my apologizes for the delay.

You can take a look at the fix and follow along in: #3189 and #3192

You will still need libc6-compat, but other than that it should work totally fine on alpine

[weyert]

Awesome, thank you, let me know when you want me to try it out :)

[tknickman]

Latest canary is working in Alpine - we're doing a bit more testing before a full release, but it's close enough to bang on a bit

[ronaldburns]

Been following this issue as we've had the same problem. Can confirm 1.7.0-canary.7 has fixed this for us.
Thank you!

[tknickman]

Thanks for testing this out @ronaldburns / @weyert! We really appreciate it.

I'm going to close this for now (1.7.0 should be landing in the next day or two) - but please open a new issue or comment here if you see any other issue with the canary in Alpine!