Segfault on Google's Container Optimized OS (which uses musl vs glibc)

[Nagyman]

How can we reproduce the crash?

Not sure if any of this helps and I can't provide access to all code.

Running environment:

• Google Batch Job -> Google Compute Engine -> Container Optimized OS
• Docker container oven/bun:latest (no real customizations) - full docker file pasted below
• The crash happens somewhere during data retrieval (network requests), using Prisma as the ORM.
• UPDATE: The crash seems to happen when using ExcelJS

Dockerfile

FROM oven/bun:latest AS runner
WORKDIR /workspace

ARG NODE_ENV="production"
ENV NODE_ENV=${NODE_ENV}

COPY package.json bun.lock ./
COPY apps/op/package.json apps/op/package.json
COPY . .

WORKDIR /workspace/apps/op

RUN bun install
RUN bunx prisma generate

CMD ["bun", "run", "jobs", "worker", "--ttl=240_000"]

Logs from the crash. There is plenty of memory on the machine, so something else is up.

Relevant log output

Stack Trace (bun.report)

Bun v1.2.4 (fd9a5ea) on linux x86_64_baseline [RunCommand]

Segmentation fault at address 0x00000000

• ld-temp.o:0: icudt75_dat
• ld-temp.o:0: icudt75_dat

Features: tsconfig, tsconfig_paths, process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, fetch, jsc

_{Sentry Issue: BUN-A43}

[Jarred-Sumner]

Is "Container Optimized OS" a musl or glibc ? Maybe the installed native addon is musl but the bun version is glibc?

[Nagyman]

@Jarred-Sumner actually think we may be able to close this. I found another closed issue here #17897 from last week that is almost an identical situation, including running ExcelJS.

We were using oven/bun:latest so I'm re-trying with oven/bun:1.2.3

[Nagyman]

To clarify Container Optimized OS is from Google Engine Compute. https://cloud.google.com/container-optimized-os/docs

[Nagyman]

Same issue in Bun v1.2.3 (8c4d3ff) Linux x64 (baseline)

Trying 1.2.2

[Nagyman]

Is "Container Optimized OS" a musl or glibc ? Maybe the installed native addon is musl but the bun version is glibc?

Google Container Optimized OS uses musl as its standard C library, not glibc

[Nagyman]

I'm getting the same issue regardless of bun version (including canary).

I used a different boot disk instead in (allocationPolicy.instances[]) as part of the Google Batch specification e.g.:

{
  allocationPolicy: {
    instances: [{
      policy: {
        ...
        bootDisk: {
          // gcloud compute images list --project=batch-custom-image --no-standard-images
          image: 'projects/batch-custom-image/global/images/family/batch-debian-11-official',
        },
      }
    }]
    ...
  }
}

And it worked 🥳

So there's something in the default Container Optimized OS that Goole uses as the default boot image when the runnable is a docker container.

[Nagyman]

I'll close this as there's a workaround.

[Electroid]

Even if there’s a workaround, if Bun crashes, we’ll need to fix it.