This is an automated email from the ASF dual-hosted git repository. maximebeauchemin pushed a commit to branch compose_version in repository https://gitbox.apache.org/repos/asf/superset.git
commit 14726c59e4f2973376eed4ccde2d3cc599991ecb Author: Maxime Beauchemin <[email protected]> AuthorDate: Tue Apr 8 12:40:24 2025 -0700 docs: clarify docker-compose-image-tag instructions People get confused around running older versions of Superset with `docker-compose`, this should help a bit. Now note that the solution here would be to NOT mount the `docker/` folder as a volume, but would required new releases/docker images with the proper ADD inststruction in the docker file. Personally can't commit the time/effort to go pull these old branches and producing new builds. Another solution is to do this so that releases, moving forward, would be more self-contained. NOTE: adding new runnable scripts inside images has some security implications, probably need to think through which scripts are runnable/executable by which users (`superset` and `root`) and get this right. --- docs/docs/installation/docker-compose.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/installation/docker-compose.mdx b/docs/docs/installation/docker-compose.mdx index 499ad41364..ef4c823521 100644 --- a/docs/docs/installation/docker-compose.mdx +++ b/docs/docs/installation/docker-compose.mdx @@ -112,7 +112,11 @@ docker compose -f docker-compose-non-dev.yml up ### Option #3 - boot up an official release ```bash +# Set the version you want to run export TAG=3.1.1 +# Checkout the corresponding git ref +git checkout $TAG +# Fire up docker compose docker compose -f docker-compose-image-tag.yml up ```
