Streamlit Community Cloud – APT dependency installation failure

Using Streamlit
1

Subject: Community Cloud deployment fails: expired bullseye-security Release file

Hello,

I am unable to deploy my Streamlit Community Cloud application.

App:
mbbt6x.streamlit.app

Repository:
analiza_skladki_ubezpieczeniowej

Branch:
main

Main file:
app.py

The deployment consistently fails during the APT dependency installation step, before the Python dependencies are installed.

My packages.txt contains only:

portaudio19-dev
python3-all-dev
ffmpeg

My requirements.txt contains:

pandas
plotly
streamlit
scikit-learn
pycaret==3.3.2
audiorecorder

The relevant deployment log is:

📦 Processing dependencies...
📦 Apt dependencies were installed from /mount/src/analiza_skladki_ubezpieczeniowej/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
Get:4 http://deb.debian.org/debian-security trixie-security InRelease
Get:5 https://packages.microsoft.com/debian/11/prod bullseye InRelease
Get:6 http://deb.debian.org/debian-security trixie-security/main amd64 Packages

Reading package lists...

E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 11h 5min 8s). Updates for this repository will not be applied.

installer returned a non-zero exit code
Error during processing dependencies!

I have already tried rebooting the application, but the exact same error occurs on a fresh build.

The unusual part is that the build environment appears to contain both Bullseye and Trixie repositories:

  • bullseye-security
  • bullseye Microsoft repository
  • trixie
  • trixie-updates
  • trixie-security

The expired Bullseye repository does not come from my packages.txt.

Could you please check whether the APT repository configuration of the Community Cloud build environment is incorrect or whether there is currently an issue with the Bullseye repository?

Thank you.

2

Welcome to the Streamlit community, and thanks for your detailed question! :rocket: You’re not alone—this “expired bullseye-security Release file” error is a known issue that occurs when the Debian Bullseye security repository used by Streamlit Community Cloud becomes outdated or unreachable. This is not caused by your packages.txt or requirements.txt, but by the base image and APT sources configured in the Community Cloud environment. The presence of both Bullseye and Trixie repositories is due to the platform’s current transition and is not user-configurable.

The best-practice solution, as confirmed by multiple community threads, is to delete your app and redeploy it. This forces Streamlit Community Cloud to re-provision the environment, often resolving expired repository issues. If the problem persists after redeployment, it means the issue is on Streamlit’s infrastructure side and will require their team to update the base image or repository configuration. You can monitor the status or report ongoing issues via the Streamlit Community forums or Community Cloud status page. For more details, see similar reports and resolutions in the community: Packages.txt deployment issue, Debian repo bullseye-security changed its codename, and Streamlit apps with packages.txt broken due to Debian stretch release not found.

Sources:

3

Hey @moni69,

Thanks so much for flagging. This is a known issue the team has been made aware of & the fix is currently in the works! :rocket:

4

Hey @moni69 , 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: