App deployment failing — bullseye-security InRelease is expired during apt dependency install

Community Cloud
,
1

Hi, my app has been failing to deploy consistently over the last few hours due to an apt-get error during the dependency installation step. This appears to be an issue with the base container image’s Debian security repo, not my own code or dependencies.

App URL: https://iadai201-1000408-sriprasath-p-safefall-ai-wyaamwgmanzxpnngdjhf.streamlit.app/
Repo: GitHub - sri133/IADAI201-1000408-Sri_Prasath-P-SafeFall-AI · GitHub , branch main

Error log:

📦 Processing dependencies...
📦 Apt dependencies were installed from packages.txt using apt-get.
Hit:1 http://deb.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Get:3 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
Get:4 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
Get:5 https://packages.microsoft.com/debian/11/prod bullseye InRelease [3650 B]
Get:6 https://packages.microsoft.com/debian/11/prod bullseye/main amd64 Packages [312 kB]
Get:7 http://deb.debian.org/debian-security trixie-security/main amd64 Packages [252 kB]
Get:8 https://packages.microsoft.com/debian/11/prod bullseye/main arm64 Packages [130 kB]
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 7h 21min 28s). Updates for this repository will not be applied.
❗️ installer returned a non-zero exit code
❗️ Error during processing dependencies!

What I’ve tried:

  • Multiple reboots — the error persists across attempts, and the “invalid since” duration keeps increasing each time, confirming the mirror snapshot isn’t refreshing on its own.
  • Verified my packages.txt only contains standard, lightweight packages (libgl1, libglib2.0-0t64, needed for mediapipe) — nothing Microsoft or bullseye related.
  • The packages.microsoft.com/debian/11/prod (bullseye) source appears to be part of the base image itself, not something my repo pulls in.

Since this is happening at the apt-source level of the container and not something I can control from my repo, could someone from the Streamlit team take a look at the base image’s bullseye-security apt source? It seems to be serving a stale/expired InRelease file.

Thanks in advance!

2

Welcome to the Streamlit community, and thanks for the detailed report and links! :rocket: You’re absolutely right—this error is due to the Debian security repository’s InRelease file being expired, which is outside your app’s code or dependency control. The error message E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired confirms it’s a base image/mirror issue, not a problem with your packages.txt or requirements.txt.

This type of issue has occurred before and is typically resolved by the Streamlit Community Cloud team updating or refreshing their base containers to point to a valid, up-to-date Debian security repo. In similar past incidents, the recommended workaround was to delete and redeploy the app after the platform fix is rolled out, as rebooting alone won’t help while the base image is stale. For now, there’s nothing actionable on your end—just keep an eye on the Streamlit Community Cloud status page and the forums for updates. If you see a fix announced, delete and redeploy your app to pick up the new base image.

Sources:

3

Hey @SRI_PRASATH

Thanks so much for the flag! The team is aware of the issue and the fix is currently in the works. :rocket:

4

Hey @SRI_PRASATH , thanks for reporting the issue to us! We have rolled out a new version to prod which should fix the issue! Please let us know if something is still not working and sorry for the inconvenience :slight_smile: