Add an explicit no-op option for minimal containers that do not have echo#516
Add an explicit no-op option for minimal containers that do not have echo#516vizowl wants to merge 2 commits intodocker:masterfrom dragonfly-science:master
Conversation
Signed-off-by: Christopher Knox <[email protected]>
|
I messed up the code signoff so I will create a new pull request with a rebased commit ... |
|
Was there a new PR for this? This issue still persists. |
|
I only closed this pull request because I messed up the commit signing - there was another pull request here #517 which generated a lot of discussion but no solution. I just stopped using minimal containers for data only volumes ... |
|
@vizowl Could I open a new PR with your code and sign off of it? I would love to GTM. |
|
If anyone else if having this problem, you can use the |
|
@saulshanabrook A preferred solution would be the one proposed in #874 - use container renaming so we don't have to have intermediate containers at all. |
Docker-compose requires images to have teh "echo" command, which the `true` image doesn't so use a different minimal image that has this command. workaround for docker/compose#516
4 participants
In order to support data only volumes using minimal images #514 I have added an option that allows a no-op command to be explicitly specified - currently it is assumed to be
echowhich isn't necessarily available on a minimal image.I have added a test and updated the documentation.
I am concerned that this approach essentially exposes an internal feature ...