Open apoorvam opened 4 years ago
Solution 1:
Combine all user commands and pass it as default command(instead of current tail -f /dev/null
as default command to create container) to execute the shell script
Cons:
Solution 2:
Find the entrypoint and override it with bash
or cmd
based on OS
Will research more on how this can be fixed and post update.
Resetting entrypoint seems to fix this issue. PR: https://github.com/leopardslab/dunner/pull/176
What if the entry point is something like /app/src/python/main/analyze.py
? Then someone who uses this docker needs to put this again and again in commands, right?
tasks:
release:
steps:
- image: SCoRe/MLKit
commands:
- ["/app/src/python/main/analyzer.py", "analyze", "--algo","ImageNet"]
Right, no default command/args will be set. User will have to use it in shell mode and not as an executable. @agentmilindu
Is some cases, users really don't know what is the entry point is. I strongly suggests against users having to define the entry point in commands.
WDYT @PratikDhanave @tdevinda @charithccmc @tharindupr @rehrumesh?
For Docker images whose entrypoint is defined and are run as an executable, Dunner fails to execute commands defined in it.
Example: Goreleaser's docker file.
Dunner task file:
Running this command with dunner fails with error as: