hey man i'm exactly having the same issue and i'm now thinking that using docker compose is not possible way to do it since building process is not ordered in docker compose instead of using the docker compose just going to create a bash file and create network volues there and will do accordingly

this problem is "static site generation fails with docker compose"

Normally, wouldn't the strapi server always be running, since it acts more like a 3rd party service that stores data?

We use https://dagger.io as our post-dockerfile solution: https://github.com/hofstadter-io/hof/blob/docs/updates/next/ci/dagger.mts

It is possible to run "services" or "sidecars" during the build/test process with Dagger.

hm so separate solutions instead of composing

so intead of docker compose maybe compose.sh

for your case, just use depends_on for docker compose

yup i used it, but it doesn't re-order the builds, it just re-order the container starts

i can use healthchecks also

you should always use alive/ready probes

service_healhty?

not sure what they are in DC, we use k8s

okay but how to know if a container is initialized completely, i mean it's a separate process how the base os can know that the mysql is started in the container for example

would love to use that but we are really low on resources

knowing when a service is ready is always specific to that service

curl or ping with an interval?

whatever your services' documentation tells you

I assume strapi and mysql have something like this

strapi is not very well documented the dockerization and for mysql it's quite straight forward

The issue is that even if build depends on strapi server being running

that means it wouldn't build during container runtime

because it only has one command during runtime

like if that was even possible, it would just skip building altogether i think

a workaround might be that i build the project myself

and use docker to copy the pre existing build files

so that it doesn't need to b uild

I think I found a possible solution, in the packages.json for next.js you can edit the command you want to use for docker runtime (either "start" or create your own) and basically just add the two commands as you would usually do in packages.json, then use that command to run the container:

this should implement the wanted behavior, in which the website is built at runtime instead of build time, so that it's doing that while server is running

this is the error i'm currently facing:

ok this was just my api tokens

i think this solution should work