Support 0.9.9

[cweiske]

https://hub.docker.com/r/library/known/tags/ still has 0.9.2 as most up-to-date version. Please support 0.9.9 (https://groups.google.com/forum/#!topic/known-dev/UXPHVXBmshQ).

[pierreozoux]

@benwerd could you add: https://github.com/docker-library-bot to the collaborators, then the process would be automatised.
Thanks!

[mapkyca]

Looks like this was done in 676e8a4

[edrex]

A new image built from the dockerfile still needs to uploaded to the registry: https://hub.docker.com/_/known/

+1 for automation :D

[edrex]

It seems like something is wrong with the build bot config. When I click the "Dockerfile" link next to "latest" on https://hub.docker.com/r/library/known/, it points to an old ref from 2016. The bot is building new images, but they seem to be pinned to that ref. IDK where in the various @docker-library metadata repos this ref is set. @pierreozoux any ideas?

[edrex]

Ah here we go: https://github.com/docker-library/official-images/blob/master/library/known needs to be updated.

[pierreozoux]

@benwerd or @mapkyca could you add: https://github.com/docker-library-bot to the collaborators, then the process would be automatised.
Thanks!

[edrex]

For now I've forked this repo and set up an auto builder for my own use. https://hub.docker.com/r/pdxhub/known/

[mapkyca]

@pierreozoux ... you mean to the Known-Docker project?

[mapkyca]

... don't we just need to set up the integration..? https://docs.docker.com/docker-hub/builds/#understand-the-build-process ... or am I misunderstanding you :) (little troubled by giving third party accounts repo access, bot or no... seems like a bad way of automating something...)

[mapkyca]

I think we just need to activate the docker hub service on the github side, in which case I'll need @benwerd to do it as he has the docker account it needs to go under.

I'll give him a ping...

[pierreozoux]

Sorry that it was not clear.
It is the automation process for official images.
(for regular images, yes, then you use the docker automated builds)

For the official images, you give access to a bot that can commit on this repo.
(I think it is a Jenkins repo)

It then runs once a day I think to run the update.sh script and figure out if there is a new version.
If there is, then it updates the Dockerfile.
And at the end, it generates the stackbrew library that is used to tag the official images.

So it is really cool, as the full process is automated. You see what I mean now?
If you need details, let me know.

[pierreozoux]

@mapkyca any news on that please?

[mapkyca]

I've given the bot read access to the repo, currently awaiting a response... not sure how long that will take...

[rmdes]

any news on this ?

[mapkyca]

I added the bot as a contributor, I'm not sure what happens next..

[pierreozoux]

The bot needs write access.
@J0WI could you help us on that please?

[J0WI]

@J0WI could you help us on that please?

I'm not sure how?

[J0WI]

I just had a look on the Dockerfile and it's currently broken. I would highly recommend to add a CI to the repo that you are aware of any failures.
A PR to fix the build is right around the corner.

[mapkyca]

I've enabled write access.

[J0WI]

https://github.com/docker-library/official-images/blob/master/library/known should be updated

[mapkyca]

Assuming this is fixed now, closing