-
Notifications
You must be signed in to change notification settings - Fork 68
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
Auto-update #15
Comments
sorry for my late answer. right now the container is update manuelly. |
I think this only works with docker hub repos. But maybe i could set up a Build Trigger hook. |
Docker hub is the only place I've found your container besides GitHub. I
don't see it on quay.io. Not sure what you're saying.
…On Wed, Jul 25, 2018, 4:35 PM Mumie-hub ***@***.***> wrote:
I think this only works with docker hub repos. But maybe i could set up a
Build Trigger hook.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC8Kk-AEfPMLfXGABovp4dNhuKu87-0xks5uKNabgaJpZM4UODC8>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just wanted to drop in and say thanks for creating such a stable and reliable container for rclone. It's been the best so far.
I use Watchtower to auto stop and update a container when the Docker Hub repo creates a new build. Looks like you already have the container build being triggered by something else, most likely the rclone github repo you are pulling the package.
The text was updated successfully, but these errors were encountered: