Allow String? for 'docker' RuntimeAttribute
See original GitHub issueIn other words, we should validate docker
as an optional string so that we can do things like this:
task foo {
String? dockerName
command { ... }
runtime {
docker: dockerName
}
output { ... }
}
The expected behaviour here is:
- If
dockerName
is set, use docker and use the specified image name - If
dockerName
is not set, do not use docker.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:27 (15 by maintainers)
Top Results From Across the Web
Docker run reference
Configure containers at runtime. ... The PID Namespace removes the view of the system processes, and allows process ids to be reused including...
Read more >docker run - Docker Documentation
The docker run command first creates a writeable container layer over the specified image, and then starts it using the specified command. That...
Read more >docker service create - Docker Documentation
Use the --secret flag to give a container access to a secret. ... This option sets the docker service containers hostname to a...
Read more >Store configuration data using Docker Configs
How to store configuration data separate from the runtime. ... Docker swarm service configs allow you to store non-sensitive information, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ruchim We are getting a lot of questions about being able to run local/SGE without docker at the Spain workshop… Not just Spanish people, but from several countries.
Another point that Eric and I came across is that a “Docker in Docker” solution - i.e. installing Docker inside the Docker container where he’s running Cromwell - is not good either because it necessitates pushing and re-pulling the Docker image he’s iterating on, which makes for annoyingly long cycle times and can’t work with bad or no Internet.