[Bug]: Transferring context fails with out of space error

I have done the following

  • I have searched the existing issues
  • If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

  1. Run `container system start``
  2. Run container build --tag tadone-dev --file .devcontainer/Dockerfile .

Dockerfile:

# Stage 1: Build Angular 18 App
FROM node:22-alpine AS builder

# Install Java (for Firebase emulators)
RUN apk add --no-cache openjdk17 && java -version

RUN corepack enable pnpm
RUN corepack use pnpm@latest-10

# Set zsh as default shell
SHELL ["/bin/zsh", "-c"]

# Install Angular CLI and Firebase Tools globally
RUN npm install -g @angular/cli firebase-tools typescript

WORKDIR /app

# Copy the rest of the application files
COPY . .

# Enable Firebase experiment
RUN firebase experiments:enable webframeworks

# Expose necessary ports
EXPOSE 4200 4200
EXPOSE 4000 4000

I'm using an Angular project with node_modules and build caches.

Current behavior

While running the build command in the transferring context phase I get a out of space error.
I'm not sure this is due to the node_modules and build cache folders having too many items or being too big. I've tried deleting all caches and node_modules but still got the same error.

Expected Behavior

I'm not sure, but I expected this to succeed like docker.

Environment

- OS: macOS 26 beta 1
- swift: 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5)
- xcode: 26.0 beta (17A5241e)
- container: 0.1.0

Relevant log output

[+] Building 18.0s (1/2)                                                                                   
 => [resolver] fetching image...docker.io/library/node:22-alpine                                      0.0s
 => [internal] load .dockerignore                                                                    16.6s
 => => transferring context:                                                                         16.6s
container(35030,0x16e22f000) malloc: Failed to allocate segment from range group - out of space

Code of Conduct

  • I agree to follow this project's Code of Conduct