tvalentyn commented on PR #16658: URL: https://github.com/apache/beam/pull/16658#issuecomment-1426539767
Looks like we have users that were affected by these changes. Currently saw couple of cases, both with users who provide custom containers, patched with an entrypoint from Beam. 1) If base image doesn't have python3-venv, environment creation fails. We could fall-back on single env in this case. 2) (Likely but not confirmed) see: https://github.com/apache/beam/issues/25085. Still thinking how to respond and keeping an eye on other issues. An opt-in / opt-out capability via envrionment variable is another option. -- 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]
