Open peperunas opened 6 months ago
I had a similar issue, where I would get the exact same output if I built the image via docker-compose.
If I first build the image with:
docker build -t unsaged -f apps/web/Dockerfile . --rm
and then reference this image in my docker-compose, everything works fine.
Describe the bug The image built through the official Dockerfile does not run as expected.