[GH-ISSUE #794] Komodo containers are still on Debian GNU/Linux 11 #8686

New Issue

GiteaMirror · 2026-05-03T04:50:55-05:00

GiteaMirror commented

2026-05-03 04:50:55 -05:00

Originally created by @marrobHD on GitHub (Sep 1, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/794

Hi,

not much to say. The Komodo containers are still on Debian GNU/Linux 11 while Debian 13 is available.

It is not a huge problem, as Debian 11 is still supported until August 31, 2026.

Tho, a newer Debian would be cool for various reasons!

Originally created by @marrobHD on GitHub (Sep 1, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/794 Hi, not much to say. The Komodo containers are still on Debian GNU/Linux 11 while Debian 13 is available. It is not a huge problem, as Debian 11 is still supported until August 31, 2026. Tho, a newer Debian would be cool for various reasons!

GiteaMirror added the enhancement label 2026-05-03 04:50:55 -05:00

GiteaMirror commented

2026-05-03 04:50:56 -05:00

@mbecker20 commented on GitHub (Sep 1, 2025):

The reason is that debian buster slim images are >64 mb, while bullseye goes up to 75 mb and trixie all the way up to 100 mb. Many users would prefer the images are as small as possible while still operating correctly. Are the any improvements which the newer bases bring for you which could justify increase in size?

@mbecker20 commented on GitHub (Sep 1, 2025): The reason is that debian buster slim images are >64 mb, while bullseye goes up to 75 mb and trixie all the way up to 100 mb. Many users would prefer the images are as small as possible while still operating correctly. Are the any improvements which the newer bases bring for you which could justify increase in size?

GiteaMirror commented

2026-05-03 04:50:57 -05:00

@marrobHD commented on GitHub (Sep 1, 2025):

Hi,

i think earlier or later newer images have to be used. Later when Debian 11 isn't supported anymore.

It is likely, that not all security fixes are backported. Some issues are unknown and other are simply overlooked.

The Debian slim image is 28.39 MB big (compressed). The compressed size of debian 11 is not much different.

If the size is too big, alpine could be an alternative.

I think a change in size of 50MB is not significant for many users.
Storage is cheap and unused images can be deleted.
If you are unsure, you could do a user survey about this.

@marrobHD commented on GitHub (Sep 1, 2025): Hi, i think earlier or later newer images have to be used. Later when Debian 11 isn't supported anymore. It is likely, that not all security fixes are backported. Some issues are unknown and other are simply overlooked. The Debian slim image is 28.39 MB big (compressed). The compressed size of debian 11 is not much different. If the size is too big, alpine could be an alternative. I think a change in size of 50MB is not significant for many users. Storage is cheap and unused images can be deleted. If you are unsure, you could do a user survey about this.

GiteaMirror commented

2026-05-03 04:50:58 -05:00

@mbecker20 commented on GitHub (Sep 1, 2025):

Alpine use musl instead of glibc so isn't an option. Yes it should definitely change before EOL.

@mbecker20 commented on GitHub (Sep 1, 2025): Alpine use musl instead of glibc so isn't an option. Yes it should definitely change before EOL.

GiteaMirror commented

2026-05-03 04:50:58 -05:00

@Blacks-Army commented on GitHub (Jan 7, 2026):

Alpine use musl instead of glibc so isn't an option. Yes it should definitely change before EOL.

Additionally, the Git version in Bullseye does not support SSH commit signing.

@Blacks-Army commented on GitHub (Jan 7, 2026): > Alpine use musl instead of glibc so isn't an option. Yes it should definitely change before EOL. Additionally, the Git version in Bullseye does not support SSH commit signing.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#8686