tvalentyn commented on issue #22349:
URL: https://github.com/apache/beam/issues/22349#issuecomment-1315708603

   @alxmrs Thanks a lot for circling back on this, I am not aware of anyone 
working on this feature right now.
   
   Thanks so much for volunteering to offer help here.
   
   I think it should be straightforward and reasonable to add conda support in 
Beam's docker entrypoint, but would require more consideration to actually 
include a conda-enabled image into our released artifacts as it would require 
us taking on additional support burden maintaining these images going forward, 
so we should evaluate demand pros' and pros/cons for having a conda-enabled 
image versus offering an easy container customization path for users who would 
like to build a custom conda-enabled image to use in their pipelines.
   
    Something we could start with is a conda-aware entrypoint and documentation 
how to build a custom conda-based image from a dockerfile + integration tests 
that verifies this solution continues to work. 
   
   After ironing out rough edges we could consider the more permanent solution 
and potentially releasing the conda image. I think that's how I would approach 
it currently, but this is a very good conversation to have on dev@ mailing list.
   
   Would you be interested in starting a one-pager with your proposal and 
sending it out?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to