Version out of date. about docker.official.image HOT 5 CLOSED

Yes. We will.

Each and every update and change goes through a review process, by the upper tier tech gurus at docker dot com.

It can take up to a month of elapsed time.

We will bundle 0.5 and 1.0 when 1.0 is ready.

We also need to further automate our image build workflow.

from docker.official.image.

@Sing-Li What can we do to make this process faster and automated? Do we have to create a new release every time we think it should be updated on docker official image? TIA

from docker.official.image.

@marceloschmidt Yes, need to create a build workflow (real one), so we need to:

• officially tag the release
• build it and create the tgz
• store the tgz behind our demo server (must be HTTPS)
• sign it (gabriel has the official key) and generate signature files
• generate the docker file with the appropriate release version and tgz location and signature files
• NOTE: very important - dockerfile used MUST BE the qualified OFFICIAL file with only version changes ... do not substitute any other dockerfile
• test to make sure the dockerfile actually works
• create and commit a new release (git hash to dockerfile and docs) on the official docker registry
• submit the new hash set to the committee for review (as an issue on their github repo)
• wait

All parts are automate-able except perhaps for the doc changes - may need some hand tuning.

The review pipeline is not fast enough for our frequent commits - so we really should be pushing true 'releases' only. Perhaps we can start a 2 weeks release cycle?

from docker.official.image.

Wow! What a list! So all of this is essentially so it'll be verified as legit? You'd think they would have an easier way to do this.

Maybe we can automate some of this with chatops :)

from docker.official.image.

OK ... updating with v0.7 now that we have a real working CI/CD workflow.

from docker.official.image.