QT/superset2
1
0
Fork 0
mirror of https://github.com/apache/superset.git synced 2026-08-04 04:52:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: strip leaked .po files when copying translations to custom image

Browse Source 
The intermediate build stages' own cleanup only matches single-character
extensions (a `*.[po,mo]`-style glob), so `.po` source files can still be
present when copied into a custom image. Strip them explicitly in the
documented recipe so it does what the comment says.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
rusackas
2026-07-29 22:44:55 -07:00
parent 170dd756c9
commit 83e7a8fc89
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/admin_docs/installation/docker-builds.mdx
View File

@@ -132,12 +132,14 @@ Docker can reuse the cached upstream layers and only rebuild what your stage add
FROM apache/superset:5.0.0 AS my-custom-image
USER root
# Pull the compiled translation files out of the earlier build stages. These
# only exist mid-build (frontend .json in `superset-node`, backend .mo in
# `python-translation-compiler`) and get stripped from the final `lean`/`dev`
# stages unless BUILD_TRANSLATIONS=true.
# Pull the translation files out of the earlier build stages (frontend
# .json in `superset-node`, backend .mo in `python-translation-compiler`).
# Those stages' own cleanup only matches single-character extensions, so
# the source `.po` files can still be present here; strip them explicitly
# so this stage only keeps the compiled translations.
COPY --from=superset-node /app/superset/translations superset/translations
COPY --from=python-translation-compiler /app/translations_mo superset/translations
RUN find superset/translations -name '*.po' -delete
USER superset
```