Replies: 1 comment
-
|
Hi @rchl-u, Glad you find PC useful. I think the easiest approach would be to have 2 configuration files: And then start them with: process-compose -f compose.yaml -f compose.win.yamlTo simplify that even further you can use the # ./some/dir/compose.yaml
processes:
proc1:
liveness_probe:
exec:
command: '[ $(docker inspect -f "{{.State.Running}}" dozzle) = true ]'
# ./some/dir/compose.win.yaml
extends: "compose.yaml"
processes:
proc1:
liveness_probe:
exec:
command: <the Windows version of your command>And start it with: process-compose -f compose.win.yamlMore info here: https://f1bonacc1.github.io/process-compose/merge/#configuration-inheritance-with-extends |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've configured process compose on Mac which worked quite well but then when trying to get the same setup working on Windows I've realized that the command used for checking liveness is likely not portable.
For example I have
to check whether docker container is running.
On windows the process is never considered ready.
How would you recommend handling issues like that? I would like the command to be portable so that it works on both (all?) operating systems. Is the only way to wrap it in some other script? For example run in through node (my project is node-based)?
Beta Was this translation helpful? Give feedback.
All reactions