-
Notifications
You must be signed in to change notification settings - Fork 940
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
image on docker has not been built #40
Comments
Yes, we used to use the auto-builds on Docker Hub. It's great, but it's designed for a certain style of Docker containers, where they're very specialised and only take a few minutes to build. Our type of image does not play well with it. A few months ago, we switched to building all our images on our own worker machines, then doing a |
OK thanks.....but the dockerfile tab in the hub has a different script. It
is shorter but with a different base. Are you saying the image is up to
date but the script is not?
…On 2 December 2016 at 19:35, Jamie Hall ***@***.***> wrote:
Yes, we used to use the auto-builds on Docker Hub. It's great, but it's
designed for the a certain style of Docker containers, where they're very
specialised and only take a few minutes to build. Our type of image does
not play well with it.
A few months ago, we switched to building all our images on our own worker
machines, then doing a docker push to send them up to the Hub. You can
see the latest push time in the subtitle of the Docker Hub page. If you do
a docker pull kaggle/python, you'll get that latest image.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABJN6ex9dxxlejRuWTY5nMk1-zlhz6ddks5rEHMJgaJpZM4LC068>
.
|
Ah, I see what you mean — it seems that Docker Hub stopped syncing the README and Dockerfile when we turned off the auto-builds. Yes, those are stale now but the image is definitely up to date. |
The current and active versions of those files live in this very Github repo. |
OK thanks. Perhaps you can push the dockerfile too? Or if not then put a
note in there to avoid confusion.
…On 2 December 2016 at 19:41, Jamie Hall ***@***.***> wrote:
The current and active versions of those files live in this very Github
repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABJN6U9D9TpGdH3vO394qWxC7LdSPToDks5rEHRxgaJpZM4LC068>
.
|
Doesn't seem possible without destroying and recreating the repo, but I've added a clarifying note to the Readme. Thanks for pointing that out! |
The last build on docker hub is 3 months ago; and the dockerfile shown there is much smaller than the one on github. I am new to docker but I believe there is a setting to automatically build.
The text was updated successfully, but these errors were encountered: