Clear and concise description of the problem

• able to choose Node.js version
• able to choose Linux flavor
• able to choose Bun version

Suggested solution

No response

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Description of the bug

Environment

unnecessary

Steps To Reproduce

unnecessary

Additional Information

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Description of the bug

Sorry, not sure how to debug what's happening. I was testing an image a few mins ago (before the update) and everything was working, then the docker image was updated, I saw docker downloading new layers, and now bun install doesn't work anymore

#8 [ 4/11] RUN bun install --frozen-lockfile
#8 0.086 bun install v1.0.8 (2a405f69)
#8 0.089 error: Unexpected installing @remix-run/dev
#8 0.089 error: Unexpected installing @remix-run/eslint-config
.... many other packages not being installed .....
.... many other packages not being installed .....
.... many other packages not being installed .....
#8 0.118 [35.00ms] done
#8 DONE 0.1s

Environment

  System:
    OS: macOS 14.0
    CPU: (10) arm64 Apple M1 Max
    Memory: 3.79 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.0/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
    pnpm: 8.8.0 - ~/Library/pnpm/pnpm
    bun: 1.0.8 - ~/.bun/bin/bun
  Languages:
    Bash: 3.2.57 - /bin/bash
    Perl: 5.30.3 - /usr/bin/perl
    Python3: 3.9.6 - /usr/bin/python3
    Ruby: 2.6.10 - /usr/bin/ruby
  Browsers:
    Chrome: 119.0.6045.105
    Safari: 17.0
  npmPackages:
    @remix-run/dev: ^2.2.0 => 2.2.0 
    @remix-run/eslint-config: ^2.2.0 => 2.2.0 
    @remix-run/node: ^2.2.0 => 2.2.0 
    @remix-run/react: ^2.2.0 => 2.2.0 
    @remix-run/serve: ^2.2.0 => 2.2.0 
    @types/react: ^18.2.20 => 18.2.34 
    @types/react-dom: ^18.2.7 => 18.2.14 
    autoprefixer: ^10.4.16 => 10.4.16 
    eslint: ^8.38.0 => 8.53.0 
    isbot: ^3.6.8 => 3.7.0 
    miniflare: ^3.20231025.1 => 3.20231025.1 
    postcss: ^8.4.31 => 8.4.31 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    tailwindcss: ^3.3.5 => 3.3.5 
    typescript: ^5.1.6 => 5.2.2 
    vite: ^4.5.0 => 4.5.0 
    vite-tsconfig-paths: ^4.2.1 => 4.2.1 

Steps To Reproduce

FROM imbios/bun-node:20-slim
WORKDIR /usr/src/app

# Copy the package files and install dependencies
COPY . .
RUN bun install --frozen-lockfile
ENV NODE_ENV=production
RUN bun run build

Additional Information

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Description of the bug

latest tag in dockerhub should be pinned to latest-iron-debian, but currently, it's pinned to latest-current-debian.

Environment

should be not necessary

Steps To Reproduce

should be not necessary

Additional Information

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Clear and concise description of the problem

Hi,

I am trying to execute chromatic with turbosnap in alpine image but I can't because it wouldn't have git, so if would be great if this image can has git

Suggested solution

No response

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Clear and concise description of the problem

As more and more people use this docker image as their production image, testing each new build became an urgent adoption-blocking necessity.

Suggested solution

• Keep It Simple (just test the build process)
• Popular framework with build and compilation required
  • Next.js
  • Nuxt.js
  • Remix
  • Astro
  • Qwik

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Description of the bug

I'm taking advantaged of imbios/bun-node:latest to containerized my Next.js app using the Dockerfile from the example.

When I try to run the built container, it gets into error with following messages:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/local/bin/docker-entrypoint.sh": permission denied: unknown

This problem is also observed by directly building and running the Next.js app example.

I think there's some problems with the permission of /usr/local/bin/docker-entrypoint.sh in the container. By simply adding

RUN chmod +x /usr/local/bin/docker-entrypoint.sh

to the Dockerfile, the problem gets fixed.

Besides, there's a typo in the 8th line of the example Dockerfile, where bun.lockb is mistyped as bun.lock.

Environment

  System:
    OS: Linux 6.6 Arch Linux
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13600K
    Memory: 13.50 GB / 31.09 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 21.5.0 - /usr/bin/node
    npm: 10.2.5 - /usr/bin/npm
    pnpm: 8.14.0 - /usr/bin/pnpm
    bun: 1.0.21 - /usr/bin/bun
  Languages:
    Bash: 5.2.21 - /usr/bin/bash
    Java: 1.8.0_392 - /usr/bin/javac
    Perl: 5.38.1 - /usr/bin/perl
    Protoc: 25.1 - /usr/bin/protoc
    Python: 3.11.6 - /usr/bin/python
    Python3: 3.11.6 - /usr/bin/python3

Steps To Reproduce

1. Clone the repository;
2. Run cd examples/next/default-app-dir;
3. Run docker buildx build . -t next-app-example to build the image;
4. Run docker run next-app-example to run the container.

Additional Information

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Clear and concise description of the problem

Integration tests that run in each PR:

• Next.js Standalone deployment
• Astro
• Nuxt.js
• Remix
• Qwik

Suggested solution

No response

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Description of the bug

Node.js build trigger in last_nodejs.txt is in 21.

Environment

Steps To Reproduce

Additional Information

I'd recommend creating 3 separate nodejs LTS files and trigger build only the changed version.

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Description of the bug

We need to rebuild and repush each of the images containing the permission bug in #10.

TODO:

• Determine the images affected by #10
• Create a script to automate the rebuild tasks
• Run as GitHub Action special for #10 issue

Environment

Check related issue

Steps To Reproduce

Check related issue

Additional Information

Related:

• #10

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Thumbs-up (👍) count in each issue is considered as the value of the issue. The more thumbs-up, the more we prioritize it.

Clear and concise description of the problem

Current:

build: update versions

Proposed:

build: update images version

- bun: (canary) 1.2.0-canary, (latest) 1.1.2
- nodejs: (lts-iron) 20.3.4
- distro: alpine, debian, slim

Add description body to the commit message for better readability and history.

Suggested solution

No response

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Description of the bug

I need to use the standard debian image, but I can't with this particular setup

Environment

n/a

Steps To Reproduce

https://github.com/ImBIOS/bun-node/blob/main/20/debian/dockerfile#L1

Additional Information

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.