Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Docker Environment Dockerfile Default vs Provided
See original GitHub issueIn the current iteration the Docker Environment requires users to only provide a base image, to which is installs dependencies on. This isn’t a solid approach going forward and should accept a completely custom user Dockerfile with a default of our specified Dockerfile.
Default: I propose python:3.6 which installs our dependencies, similar to what we have now. @cicdw thoughts?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Dockerfile reference - Docker Documentation
A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image....
Read more >Setting Default Docker Environment Variables During Image ...
What if you want to specify default ENV values while building your Docker image? Do you really need to edit your Dockerfile every...
Read more >Docker Build Arguments and Environment Variables
The value of the build argument will determine the default value of the environment variable.
Read more >How to Set Docker Environment Variables {ARG and ENV}
Similar to ARG variables, the statement that defines ENV variables in Dockerfile provides the variable's definition and an optional default ...
Read more >How to use Docker Build Args and Environment Variables
Like ARG variables, the ENV can also have a default value in the dockerfile. You can override ENV values set in a Dockerfile...
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 Free
Top 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
I still think there’s lots of room for an implementation similar to what we have today, where users can provide pip/conda installable dependencies and they’re inserted into the default dockerfile. I just think that we should in addition allow fully custom dockerfiles (as long as Prefect is properly set up, which users take responsibility for).
This is similar to how dask deployments have a “PIP_EXTRAS” environment variable (might be forgetting the exact name); I’m guessing most of the time a base image + dependencies will satisfy requirements.
Closed with #1740