This repository was archived by the owner on Oct 29, 2025. It is now read-only.
fix: latest build issues #444
Merged
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.
Fixes the following issues :
DOCKER_BUILDKIT=0indocker compose buildcommand ordocker compose upcommand.network: stackfield is not required under build. This was required in legacy versions. Refer File -docker-compose.yamlReference: Docker's docker buildx build command documentation (which docker compose build now uses under the hood with BuildKit):
https://docs.docker.com/reference/cli/docker/buildx/build/#network
Reference - Missing git-init.sh and git-setup.sh and other problems #440
The following line - (File -
Dockerfile)RUN yarn db-deploy
RUN yarn --cwd packages/prisma seed-app-store
are executed even before the database container is ready or started. Hence the issue after prisma migrations.
Also as reported here - Missing git-init.sh and git-setup.sh and other problems #440
The
scripts/start.shscript already has these commands and executes after db is ready, hence removing these commands from docker file.Hence the docker build is failing at a COPY cmd while trying to copy these files.