You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by da...@apache.org on 2023/08/31 18:30:59 UTC
[beam] 01/01: Add guidance on container versioning
This is an automated email from the ASF dual-hosted git repository.
damccorm pushed a commit to branch users/damccorm/containerVersioning
in repository https://gitbox.apache.org/repos/asf/beam.git
commit 3a8ea9dcf341e693bfe66cd786e1e76ab9daf8b8
Author: Danny McCormick <da...@google.com>
AuthorDate: Thu Aug 31 14:30:48 2023 -0400
Add guidance on container versioning
---
website/www/site/content/en/documentation/runtime/environments.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/website/www/site/content/en/documentation/runtime/environments.md b/website/www/site/content/en/documentation/runtime/environments.md
index 554d471da98..4b027fba36c 100644
--- a/website/www/site/content/en/documentation/runtime/environments.md
+++ b/website/www/site/content/en/documentation/runtime/environments.md
@@ -298,6 +298,11 @@ python -m apache_beam.examples.wordcount \
{{< /runner >}}
+You should always specify a versioned container sha or tag, not `latest` or
+another mutable tag. This will ensure that pipelines can be easily reproduced. For
+distributed runners that spin up workers during pipeline execution, this will also
+ensure that pipelines do not switch container images in the middle of execution.
+
### Troubleshooting