Skip to content

Conversation

@SteveGilvarry
Copy link

Trying to see if we can use latest, rolling and devel to avoid needing a add a folder for new releases as soon as they are released.

Trying to see if we can use latest, rolling and devel to avoid needing a add a folder for new releases as soon as they are released.
@Totktonada
Copy link
Member

We primarily use these images to build a package for a particular Linux distribution with fixed versions of libraries (fixed to a set of ABI compatible versions). Packages built on a rolling image will break at some moment in a future, because the rolling distro will be updated in a ABI incompatible way (it is natural for rolling distros).

Next, rolling images needs periodic updates and it is a manual work now. If we want to support them, we surely need some images build/push automation.

(Maybe we should drop fedora/rawhide and debian/sid, because dockerhub images are not updated for a long time and the presence of dockerfiles in the repository may be just confusing. Or actually update them periodically.)

I don't mind to make some effort in this direction, but I would start the discussion with your scenario.

@Totktonada Totktonada added the needs feedback Waits for information from the topic starter label Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs feedback Waits for information from the topic starter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants