-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: automated publishing to Docker Hub #6591
Comments
@xoriole , when was the last time we built Docker image? Why did we stop to do so? Was it too hard to maintain? |
Small 2024 update: PR #8108 introduces automatic publishing to GitHub Packages. |
The latest main version of Tribler is now available here: https://github.com/Tribler/tribler/pkgs/container/tribler Actually pushing to Docker hub is still TODO but that should not be too much additional work. |
@qstokkink this doesn't seem to work properly? None of the 8 series are pushed as containers. An optimal setup would build and push stable releases to the :latest tag but also versioned :tags would be cool. Quite common to have some kind of :dev tag for bleeding edge as well. Also it would be nice with some docs on how to use the containers, especially now that the 8 series are released with the headless setup and web ui. |
You are right: currently, the Docker GitHub package is "barely functional" and stuck to the bleeding edge version. Getting everything packed with proper builds and tags, is something I plan to get done for the 8.1.0 release. I also want to bring back |
Alright, this is going to take a bit longer than expected: we lost control of the |
Hello, I hope this finds you well.
Please could you add an action to this repository that would automatically make it publish new releases to Docker Hub? The availability of an image on Docker Hub allows for greater portability and ease with which to use and extend Tribler (for example, to run Tribler in a container and interact with it via its API). I see you have existing images on Docker Hub, but all of them are several years old and out of date. By making an action to publish an image to Docker Hub automatically, this problem would be solved. It would remove the overhead of manually publishing images with each release (or alternatively not doing so and the image becoming out of date). The following links give some more context as to how this could be achieved:
Thank you for your time and consideration.
The text was updated successfully, but these errors were encountered: