Production Build Issue: Empty Project about symfony-docker

[maxhelias]

Anyway, this issue is not being followed up by its author. I therefore close the subject

[maxhelias]

In fact, build is for creating container and up for running it. Use the same starter but with the build.

docker compose -f compose.yaml -f compose.prod.yaml build --no-cache

Note: Don't forget the env variables before the command in both cases

[maxhelias]

It's difficult to help you with so little information. You'll have to dig a little deeper to give us the details of what's going on.

[Aweptimum]

I ran into the same issue. It seemed like my source wasn't being copied over to the production container volume, because I was only finding the symfony/skeleton inside.

However, this is the command I was using to build the production image:

docker compose -f compose.yaml -f compose.prod.yaml up

I had removed the skeleton sections from compose.yml and the entrypoint, but I forgot that the entrypoint is part of the image. So what worked was to tell docker to rebuild the image by passing --build (and a --force-recreate to be sure)

docker compose -f compose.yaml -f compose.prod.yaml up --build --force-recreate

I found the modified entrypoint, my project, and all my real dependencies had made it.

I believe this is why this other person was missing Twig from their project #479 (comment) (they have a fresh skeleton composer.json), and the source of the trouble in #521

Hopefully this solves the issue, but it's kinda just PEBCAK

[maxhelias]

@Aweptimum

However, this is the command I was using to build the production image:

docker compose -f compose.yaml -f compose.prod.yaml up

Unfortunately this is not the docker build command.. That why we add a caution in the doc :

PEBCAK has a hard skin 😅

[Aweptimum]

Right, docker build --no-cache is what should actually be done
But it's strange that the docker compose -build command seemed to work 🤔