fix: resolve sharp lib dependency issue in docker image#38
Merged
dannytlake merged 1 commit intomainfrom Mar 26, 2024
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for composable-ui-storefront canceled.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a library dependency issue error when building the docker image by executing
docker-compose up --buildin the root directory:This is due to node image
node:18-alpinemissing the required libraries to runsharp, which is needed by the Next.js Image componentTo resolve this, the Dockerfile is being updated to build from
node:18-bookworm.For an in depth guide on running Next.js in a Docker container, review the official Vercel example with-docker on how you can orchestrate building the container.