-
Notifications
You must be signed in to change notification settings - Fork 47
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
Chaining commands doesn't work anymore #124
Labels
Comments
Hi Denis, |
No worries @bibendi I'll also try to see if I find a better solution. Take your time, we will stay on |
1 task
3 tasks
Fixed at 7.1.0 |
Awesome thanks! I'll try this next week :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The fix for #113 broke our own
dip.yml
s with no beautiful way to fix it.We have many command chains in them like
command: nvm use 12 && nvm run test
. Since #113, the second part of the command will be executed on the host and not inside the container. Also note that it also breaks any backtick ` as the command will be ran on the host.To Reproduce
entrypoint.sh:
Dockerfile:
docker-compose.yml
dip.yml
All output are created with
DIP_ENV=debug
With
dip 6.1.0
(expected behaviour)dip test_chain
dip test_backquote
With
dip 7.0.1
(new behaviour)dip test_chain
dip test_backquote
Context
Workaround and proposed solution
There's a workaround that works for us but makes the
dip.yml
quite ugly. We could wrap any command in'''original command'''
or"'original command'"
. This work around works both in6.1
and7.0
.The solutions I can see are:
dip.yml
, for aninteraction
specifyingsafe: true
will automatically wrap the command in quotes., a
||or a
&&` in the command and then automatically wrapping.In any case, if we can find a solution that works for everyone I will gladly make the PR for this.
The text was updated successfully, but these errors were encountered: