-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
command is truncated from docker-compose file #109
Comments
this already shows that while parsing $$? or $$i seems to be interpreted. So the command isn't truncted like i thought but those vars seem to be replaced by empty strings. |
Here is written that you can use $$a to escape the $ sign to get the original var. But that does not work in podman-compose. https://docs.docker.com/compose/compose-file/#variable-substitution |
OK bug is in rec_subs - this function breaks the command. |
I'M not sure whether this really fixes this bug but using a negative look behind fixes my situation:
|
While this fixes the problem that a "wrong" command is shown in ps -a it still does not fix the issue that podman cannot parse it. Now ps -a looks right but podman still logs:
But manually executing the command works fine. |
OK but this again is also an issue in podman-compose. the printed podman command from podman-compose is:
while this fails if podman-compose executes it it works fine if manually executed |
OK the next problem is that podman-compose just splits the command here: but this won't work you cannot simply split this like you want. |
We can simply fix this by using shlex. will work fine |
Complete patch to fix both bugs:
|
@disaster123 Please send me pull request |
The PR has been merged. So can this issue be closed? |
Hi,
i've the following compose file:
But the container start fails with a syntax error and podman ps -a shows:
so the comand got truncated and last chars are missing:
$s)'
Greets,
Stefan
The text was updated successfully, but these errors were encountered: