slimtoolkit / slimtoolkit/slim
in the carbon example, /node_modules/next/dist needs to be explicitly included
Open
Nobody has claimed this yet.
triage
WIP
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
the carbon example isn't working as expected.
according to this comment, I thought I don't need to explicitly include (part of) node_modules.
Actual Behavior
I need to have /node_modules/next/dist to be explicitly included.
Steps to Reproduce the Problem
- docker pull
yuuuxt/carbon:4.8.1(docker hub,Dockerfile) - (not working)
docker-slim build --copy-meta-artifacts . --include-path=/app/carbon/.next --include-path=/app/carbon/public yuuuxt/carbon:4.8.1 - (working)
docker-slim build --copy-meta-artifacts . --include-path=/app/carbon/.next --include-path=/app/carbon/public --include-path=/app/carbon/node_modules/next/dist yuuuxt/carbon:4.8.1
Specifications
- Version: 1.36.1
- Platform: WSL2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the carbon example, its linked Dockerfile, and the two docker-slim build commands in the reproduction steps. Compare the failing command with the working command that explicitly includes /app/carbon/node_modules/next/dist, then verify that the carbon image builds and runs without that extra include path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, next.js, node.js
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100