Replies: 1 comment
-
Hello ... just sharing :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a SPA React app wrapped in a Dockerfile to run the build, produce static files, and place them in a pre-mounted volume (which is also mounted to a separate backend resource to host them). The frontend and backend are in separate repositories; the only connection point is a shared volume. This setup is not a monorepo with a compose file. The problem is to perform the build inside the Docker container once and then stop it.
Obviously, a container whose purpose is to run the build command will exit when done, but Coolify tries to restart it in a loop. How do I prevent it from restarting on resource exit? Apparently, I need to pass the
--restart=no
flag, but according to the docs, I can only pass these flags:Flags:
Restarting:
Running
docker update --restart=no container-abc-12345
works just fine; the resource goes into theExited
state in the dashboard. I hope this is not the only solution (or at least tell me how to run this command in the pipeline, not manually) 🙏*test front build repo - https://github.com/SanariSan/coolify-f
Beta Was this translation helpful? Give feedback.
All reactions