You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@superset.apache.org by "beatum (via GitHub)" <gi...@apache.org> on 2026/08/31 07:07:23 UTC

[PR] Enhance Podman compatibility and add development files [superset]

beatum opened a new pull request, #43705:
URL: https://github.com/apache/superset/pull/43705

**Enhance Podman compatibility and add development files**

- **Summary:** Adds Podman-ready development artifacts and Podman-specific fixes so the project can be built and run using Podman (instead of Docker) for local development and CI. Changes include a Podman Containerfile, a Podman Compose file, and a helper script; environment variables, APT behavior, mounts, and service URLs were adjusted for Podman compatibility.

- **Files added:** Containerfile.podman, create-podman-superset-files.sh, docker-compose.podman.yml

- **Key changes**
- Enforce IPv4 for APT to avoid network failures under Podman.
- Adjust volume mounts and paths to match Podman semantics and permissions.
- Update service/host URLs and environment variables for Podman networking.
- Add an executable helper script to scaffold Podman dev files and permissions.
- Add a Podman Compose file mirroring the Docker Compose dev setup but tuned for Podman.

- **How to validate**
- Build image:
```bash
podman build -f Containerfile.podman -t superset:podman-dev .
```
- Start services:
```bash
podman compose -f docker-compose.podman.yml up -d
```
- Healthcheck:
```bash
curl -f http://localhost:8088/health
```

--
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "netlify[bot] (via GitHub)" <gi...@apache.org>.

netlify[bot] commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5506839910

   ### <span aria-hidden="true">✅</span> Deploy Preview for *superset-docs-preview* ready!
   
   
   |  Name | Link |
   |:-:|------------------------|
   |<span aria-hidden="true">🔨</span> Latest commit | 7931a4812ee8b2539803ed07ff3d53184aefb02f |
   |<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/projects/superset-docs-preview/deploys/6a97dfb56353d80008278a1c |
   |<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-43705--superset-docs-preview.netlify.app](https://deploy-preview-43705--superset-docs-preview.netlify.app) |
   |<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTQzNzA1LS1zdXBlcnNldC1kb2NzLXByZXZpZXcubmV0bGlmeS5hcHAifQ.8xjECcF6M5epTQwcalB8a1STGl1O_Y-XCAkJEKloSjo)<br /><br />_Use your smartphone camera to open QR code link._</details> |
   |<span aria-hidden="true">🤖</span> Make changes | [Run an agent on this branch](https://app.netlify.com/projects/superset-docs-preview/agent-runs#q1YqKMrPLShRslJS0lFKKkrMS84AsnMTi0tSi4AiKakFOfmVnilAMbNES_OUtCRTM2NT4xQLAwMDCyNzi0TDZKVaAA) |
   ---
   <!-- [superset-docs-preview Preview](https://deploy-preview-43705--superset-docs-preview.netlify.app) -->
   _To edit notification comments on pull requests, go to your [Netlify project configuration](https://app.netlify.com/projects/superset-docs-preview/configuration/notifications#deploy-notifications)._


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] feat(podman): enhance Podman compatibility and add development files [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.

rusackas commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5612542972

   Thanks for fixing the service-worker COPY. Couple of things since though: it's showing conflicts against `master` now, and the Netlify docs check is failing. Also, the Dockerfile itself lost its `BUILDPLATFORM` arg and `--platform` pin as part of this diff, that looks unrelated to the Podman work and could affect multi-arch builds. Can you rebase and confirm that was intentional?
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] feat(podman): enhance Podman compatibility and add development files [superset]

Posted by "beatum (via GitHub)" <gi...@apache.org>.

beatum commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5578226979

> The service-worker.js COPY is missing from `Containerfile.podman` (line 218 just leaves the comment) — podman builds will 404 on it in production, per bito's flag. Also curious whether @hainenber's ask about one template across runtimes was considered instead of maintaining two Containerfiles/composes via a sed/python generator script. That's a lot of drift risk to take on.

Thank you for catching the missing service-worker.js COPY. That was an oversight on my side, and i have fixed it.
I also appreciate the recommendation to generate both runtime-specific files from one shared template. i agree that maintaining two Containerfiles and Compose files introduces drift risk. My initial reason for separating them was that podman, despite its strong Docker compatibility, still differs in some conventions and build behavior.
For this change, I have kept the differences minimal. I am also open to moving toward a shared template and generator in a follow-up if that is the preferred direction for the project and i hope these small Podman-specific adjustments can still be useful.

--
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.

bito-code-review[bot] commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5508928165

   AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
   
   <details>
   <summary>
   Bito Usage Guide
   </summary>
   
   **Commands**
         
   Type the following command in the pull request comment and save the comment.
         
   - `/review` - Manually triggers an incremental AI Review.
   - `/review full` - Manually triggers a full AI Review.
   
   - `/pause` - Pauses automatic reviews on this pull request.
   - `/resume` - Resumes automatic reviews.
   - `/resolve` - Marks all Bito-posted review comments as resolved.
   - `/abort` - Cancels all in-progress reviews.
   
         
   Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
         
   **Configuration**
   
   This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
         
   **Documentation & Help**
   - <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
   - <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
   - <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
   - <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
   
   </details>
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "hainenber (via GitHub)" <gi...@apache.org>.

hainenber commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5475987765

   Thanks for opening out this PR but have you encountered any issue when running current containerized Superset setup with Podman? I'd like to have one template to be usable across all container runtime, if possible?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.

bito-code-review[bot] commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5474953235

   AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] feat(podman): enhance Podman compatibility and add development files [superset]

Posted by "beatum (via GitHub)" <gi...@apache.org>.

beatum commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5613949957

> Thanks for fixing the service-worker COPY. Couple of things since though: it's showing conflicts against `master` now, and the Netlify docs check is failing. Also, the Dockerfile itself lost its `BUILDPLATFORM` arg and `--platform` pin as part of this diff, that looks unrelated to the Podman work and could affect multi-arch builds. Can you rebase and confirm that was intentional?

Thank you. Here is my latest update:

Rebased master onto origin/master and restored the Dockerfile to match the upstream version.
Confirmed that removing BUILDPLATFORM and --platform was intentional. Commit 7575af60c6 (fix(docker): remove unnecessary BUILDPLATFORM argument from Dockerfile) introduced this change.
Identified an unstaged local change in package-lock.json as the cause of the earlier conflict. I have left the change uncommitted.

--
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.

bito-code-review[bot] commented on code in PR #43705:
URL: https://github.com/apache/superset/pull/43705#discussion_r3892572826


##########
Containerfile.podman:
##########
@@ -0,0 +1,293 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+######################################################################
+# Node stage to deal with static asset construction
+######################################################################
+ARG PY_VER=3.11.14-slim-trixie
+
+
+# Include translations in the final build
+ARG BUILD_TRANSLATIONS="false"
+
+######################################################################
+# superset-node-ci used as a base for building frontend assets and CI
+######################################################################
+FROM node:24-trixie-slim AS superset-node-ci
+RUN printf '%s\n' 'Acquire::ForceIPv4 "true";' > /etc/apt/apt.conf.d/99force-ipv4
+ARG BUILD_TRANSLATIONS
+ENV BUILD_TRANSLATIONS=${BUILD_TRANSLATIONS}
+ARG DEV_MODE="false"           # Skip frontend build in dev mode
+ENV DEV_MODE=${DEV_MODE}
+
+COPY docker/ /app/docker/
+# Arguments for build configuration
+ARG NPM_BUILD_CMD="build"
+
+# Install system dependencies required for node-gyp
+RUN /app/docker/apt-install.sh build-essential python3 zstd
+
+# Define environment variables for frontend build
+ENV BUILD_CMD=${NPM_BUILD_CMD} \
+    PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
+
+# Run the frontend memory monitoring script
+RUN /app/docker/frontend-mem-nag.sh
+
+WORKDIR /app/superset-frontend
+
+# Create necessary folders to avoid errors in subsequent steps
+RUN mkdir -p /app/superset/static/assets \
+             /app/superset/translations
+
+# Harden `npm ci` against transient npm-registry network blips (e.g. ECONNRESET),
+# which otherwise fail the entire multi-platform image build with no retry.
+ENV npm_config_fetch_retries=5 \
+    npm_config_fetch_retry_mintimeout=20000 \
+    npm_config_fetch_retry_maxtimeout=120000 \
+    npm_config_fetch_timeout=600000
+
+# Mount package files and install dependencies if not in dev mode
+# NOTE: we mount packages and plugins as they are referenced in package.json as workspaces
+# ideally we'd COPY only their package.json. Here npm ci will be cached as long
+# as the full content of these folders don't change, yielding a decent cache reuse rate.
+# Note that it's not possible to selectively COPY or mount using blobs.
+RUN --mount=type=bind,source=./superset-frontend/package.json,target=./package.json \
+    --mount=type=bind,source=./superset-frontend/package-lock.json,target=./package-lock.json \
+    --mount=type=cache,target=/root/.cache \
+    --mount=type=cache,target=/root/.npm \
+    if [ "${DEV_MODE}" = "false" ]; then \
+        npm ci; \
+    else \
+        echo "Skipping 'npm ci' in dev mode"; \
+    fi
+
+# Runs the webpack build process
+COPY superset-frontend /app/superset-frontend
+
+######################################################################
+# superset-node is used for compiling frontend assets
+######################################################################
+FROM superset-node-ci AS superset-node
+
+# Build the frontend if not in dev mode
+RUN --mount=type=cache,target=/root/.npm \
+    if [ "${DEV_MODE}" = "false" ]; then \
+        echo "Running 'npm run ${BUILD_CMD}'"; \
+        npm run ${BUILD_CMD}; \
+    else \
+        echo "Skipping 'npm run ${BUILD_CMD}' in dev mode"; \
+    fi;
+
+# Copy translation files
+COPY superset/translations /app/superset/translations
+
+# Build translations if enabled, then cleanup localization files
+RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
+        npm run build-translation; \
+    fi; \
+    rm -rf /app/superset/translations/*/*/*.[po,mo];
+
+
+######################################################################
+# Base python layer
+######################################################################
+FROM python:${PY_VER} AS python-base
+RUN printf '%s\n' 'Acquire::ForceIPv4 "true";' > /etc/apt/apt.conf.d/99force-ipv4
+
+ARG SUPERSET_HOME="/app/superset_home"
+ENV SUPERSET_HOME=${SUPERSET_HOME}
+
+RUN mkdir -p ${SUPERSET_HOME}
+RUN useradd --user-group -d ${SUPERSET_HOME} -m --no-log-init --shell /bin/bash superset \
+    && chmod -R 1777 ${SUPERSET_HOME} \
+    && chown -R superset:superset ${SUPERSET_HOME}
+
+# Some bash scripts needed throughout the layers
+COPY --chmod=755 docker/*.sh /app/docker/
+
+RUN pip install --no-cache-dir --upgrade uv
+
+# Using uv as it's faster/simpler than pip
+RUN uv venv /app/.venv
+ENV PATH="/app/.venv/bin:${PATH}"
+
+######################################################################
+# Python translation compiler layer
+######################################################################
+FROM python-base AS python-translation-compiler
+
+ARG BUILD_TRANSLATIONS
+ENV BUILD_TRANSLATIONS=${BUILD_TRANSLATIONS}
+
+# Install Python dependencies using docker/pip-install.sh
+COPY requirements/translations.txt requirements/
+RUN --mount=type=cache,target=/root/.cache/uv \
+    . /app/.venv/bin/activate && /app/docker/pip-install.sh --requires-build-essential -r requirements/translations.txt
+
+COPY superset/translations/ /app/translations_mo/
+RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
+        pybabel compile --use-fuzzy -d /app/translations_mo || true; \
+    fi; \
+    rm -f /app/translations_mo/*/*/*.[po,json]
+
+######################################################################
+# Python APP common layer
+######################################################################
+FROM python-base AS python-common
+
+ENV SUPERSET_HOME="/app/superset_home" \
+    HOME="/app/superset_home" \
+    SUPERSET_ENV="production" \
+    FLASK_APP="superset.app:create_app()" \
+    PYTHONPATH="/app/pythonpath" \
+    SUPERSET_PORT="8088"
+
+# Copy the entrypoints, make them executable in userspace
+COPY --chmod=755 docker/entrypoints /app/docker/entrypoints
+
+WORKDIR /app
+# Set up necessary directories
+RUN mkdir -p \
+      ${PYTHONPATH} \
+      superset/static \
+      requirements \
+      superset-frontend \
+      apache_superset.egg-info \
+      requirements \
+    && touch superset/static/version_info.json
+
+# Install Playwright and optionally setup headless browsers
+ENV PLAYWRIGHT_BROWSERS_PATH=/usr/local/share/playwright-browsers
+
+ARG INCLUDE_CHROMIUM="false"
+ARG INCLUDE_FIREFOX="false"
+RUN --mount=type=cache,target=${SUPERSET_HOME}/.cache/uv \
+    if [ "${INCLUDE_CHROMIUM}" = "true" ] || [ "${INCLUDE_FIREFOX}" = "true" ]; then \
+        uv pip install playwright && \
+        playwright install-deps && \
+        if [ "${INCLUDE_CHROMIUM}" = "true" ]; then playwright install chromium; fi && \
+        if [ "${INCLUDE_FIREFOX}" = "true" ]; then playwright install firefox; fi; \
+    else \
+        echo "Skipping browser installation"; \
+    fi
+
+# Copy required files for Python build
+COPY pyproject.toml setup.py MANIFEST.in README.md ./
+COPY superset-frontend/package.json superset-frontend/
+COPY scripts/check-env.py scripts/
+
+# keeping for backward compatibility
+COPY --chmod=755 ./docker/entrypoints/run-server.sh /usr/bin/
+
+# Some debian libs
+RUN /app/docker/apt-install.sh \
+      curl \
+      libsasl2-dev \
+      libsasl2-modules-gssapi-mit \
+      libpq-dev \
+      libecpg-dev \
+      libldap2-dev
+
+# Create data directory for DuckDB examples database
+# The database file will be created at runtime when examples are loaded from Parquet files
+RUN mkdir -p /app/data && chown -R superset:superset /app/data
+
+# Copy compiled things from previous stages
+COPY --from=superset-node /app/superset/static/assets superset/static/assets
+# Copy service.worker.js optionall as it doesn't exist when DEV_MODE=true
+
+# TODO, when the next version comes out, use --exclude superset/translations
+COPY superset superset

Review Comment:
   <div>
   
   
   <div id="suggestion">
   <div id="issue"><b>Missing service-worker.js COPY</b></div>
   <div id="fix">
   
   The comment on line 212 describes copying `service-worker.js`, but the actual COPY is missing compared to the upstream `Dockerfile` (line 213). `webpack.config.js` emits `service-worker.js` to `superset/static/`, and `spa.html` registers `/static/service-worker.js` at runtime (served with a `Service-Worker-Allowed` header in `initialization/__init__.py`). Without this COPY the final image 404s on PWA registration. Restore it with the `[s]` bracket trick.
   </div>
   
   
   <details>
   <summary>
   <b>Code suggestion</b>
   </summary>
   <blockquote>Check the AI-generated fix before applying</blockquote>
   <div id="code">
   
   
   ````suggestion
   # Copy service.worker.js optionall as it doesn't exist when DEV_MODE=true
   COPY --from=superset-node /app/superset/static/service-worker.j[s] superset/static/service-worker.js
    
   # TODO, when the next version comes out, use --exclude superset/translations
   COPY superset superset
   ````
   
   </div>
   </details>
   
   
   
   </div>
   
   
   
   
   <small><i>Code Review Run #bb3a22</i></small>
   </div>
   
   ---
   Should Bito avoid suggestions like this for future reviews? (<a href=https://alpha.bito.ai/home/ai-agents/review-rules>Manage Rules</a>)
   - [ ] Yes, avoid them



-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] feat(podman): enhance Podman compatibility and add development files [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.

rusackas commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5573781969

   The service-worker.js COPY is missing from `Containerfile.podman` (line 218 just leaves the comment) — podman builds will 404 on it in production, per bito's flag. Also curious whether @hainenber's ask about one template across runtimes was considered instead of maintaining two Containerfiles/composes via a sed/python generator script. That's a lot of drift risk to take on.


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] Enhance Podman compatibility and add development files [superset]

Posted by "beatum (via GitHub)" <gi...@apache.org>.

beatum commented on PR #43705:
URL: https://github.com/apache/superset/pull/43705#issuecomment-5476457916

   > Thanks for opening out this PR but have you encountered any issue when running current containerized Superset setup with Podman? I'd like to have one template to be usable across all container runtime, if possible?
   
   Thanks for the feedback. So far, I haven’t encountered any issues running the current containerized Superset setup with Podman. The build completed successfully on my Fedora 43 Workstation. I’m also happy to help test any changes intended to make the template compatible with multiple container runtimes.
   <img width="923" height="385" alt="Screenshot From 2026-06-09 15-21-33" src="https://github.com/user-attachments/assets/4043974c-2ac1-4c18-9352-2fbc1f54676a" />
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [PR] feat(podman): enhance Podman compatibility and add development files [superset]

Posted by "beatum (via GitHub)" <gi...@apache.org>.

beatum closed pull request #43705: feat(podman): enhance Podman compatibility and add development files
URL: https://github.com/apache/superset/pull/43705


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org