-
Notifications
You must be signed in to change notification settings - Fork 20
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
Push to dockerhub #63
Conversation
I assume the tag still must be created using https://github.com/ome/omero-web-docker/blob/master/Makefile i.e. replacing the variables and effectively, this replaces the |
The tag needs to be created and pushed cf. description. The changes follow a similar approach that the one taken in omero-server-docker and replace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The images pushed to https://hub.docker.com/r/jburel/omero-web/tags and https://hub.docker.com/r/jburel/omero-web-standalone/tags have exactly the same checksums and sizes. I assume the build step needs to specify which Dockerfile should be used for each image, which in turn might speak for creating two upload workflows rather than combining them into one.
I realised that afterwards. I am going to slip things up |
@sbesson problem is now fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updated logic makes sense although I haven't functionally tested the generated images. Getting it in will certainly automate part of the update of these images and reduce the manual load.
I share some of the re-usability concerns expressed here and in #64 (comment). In the case of these images. I assume the only way to reduce the customization of the workflow would be to extract the standalone Docker files into its own repository.
As indicated previously during discussion, |
But the extraction will break the workflow that is proposed in this PR. So I guess the question is whether we want to extrac first or capture as an issue and come back to it? |
If we extract, of course the workflow will need to be reviewed. The proposed changes automate the build/push of the images. |
#53 already captures the release of apps problem. i did not notice the issue |
The commit 6d985b7 adds labels cf. in ome/omero-server-docker#57. More labels than the 3 current listed in the Dockerfile are added. List of labels:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(base) [sbesson@idr2-slot3 ~]$ docker pull jburel/omero-web:latest && docker inspect jburel/omero-web:latest | grep opencon
latest: Pulling from jburel/omero-web
Digest: sha256:e55b1e767779aa51517d979a2c8482ee83eea16e406d149ea376abae5966eeeb
Status: Image is up to date for jburel/omero-web:latest
docker.io/jburel/omero-web:latest
"org.opencontainers.image.created": "2022-03-18T11:40:23.345Z",
"org.opencontainers.image.description": " OMERO.web production docker image",
"org.opencontainers.image.licenses": "",
"org.opencontainers.image.revision": "6d985b7284edacba4f3d094d43ddeb3c3973075f",
"org.opencontainers.image.source": "https://github.com/jburel/omero-web-docker",
"org.opencontainers.image.title": "omero-web-docker",
"org.opencontainers.image.url": "https://github.com/jburel/omero-web-docker",
"org.opencontainers.image.vendor": "CentOS",
"org.opencontainers.image.version": "5.13.0-15"
(base) [sbesson@idr2-slot3 ~]$ docker pull jburel/omero-web-standalone:latest && docker inspect jburel/omero-web-standalone:latest | grep opencon
latest: Pulling from jburel/omero-web-standalone
Digest: sha256:eafffcf657c150dcaf1c715c62872fa379750f461100a9bb7fcd3046149e0025
Status: Image is up to date for jburel/omero-web-standalone:latest
docker.io/jburel/omero-web-standalone:latest
"org.opencontainers.image.created": "2022-03-18T11:40:23.345Z",
"org.opencontainers.image.description": " OMERO.web production docker image",
"org.opencontainers.image.licenses": "",
"org.opencontainers.image.revision": "6d985b7284edacba4f3d094d43ddeb3c3973075f",
"org.opencontainers.image.source": "https://github.com/jburel/omero-web-docker",
"org.opencontainers.image.title": "omero-web-docker",
"org.opencontainers.image.url": "https://github.com/jburel/omero-web-docker",
"org.opencontainers.image.vendor": "CentOS",
"org.opencontainers.image.version": "5.13.0-15"
Looks good. Can you clean up the corresponding LABEL
statements from the Dockerfile
for both images?
The redundancy of org.opencontainers.image.title
and other metadata is probably an indicator that we will need to extract the standalone
image eventually
@sbesson I have cleaned up the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few potential follow-ups mentioned in the thread worth capturing as issues but otherwise I am fine for this to get merged to start making incremental improvement of our deployment workflow
@@ -34,8 +34,6 @@ ifndef VERSION | |||
endif | |||
|
|||
perl -i -pe 's/OMERO_VERSION=(\S+)/OMERO_VERSION=$(VERSION)/' Dockerfile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I cannot spot any OMERO_VERSION
left in Dockerfile
, these changes might make the Makefile
irrelevant and it can probably cleaned up as a follow-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could not spot it but I kept it "just in case"
With the automation option proposed in another PR, the Makefile
will become totally irrelevant
https://hub.docker.com/r/openmicroscopy/omero-web/ and https://hub.docker.com/r/openmicroscopy/omero-web-standalone/ have not been updated since the release of omero-web 5.11
This PR automatically will push to dockerhub when a tag is pushed to this repo
cc @sbesson @will-moore
Tested using my account see https://hub.docker.com/r/jburel/omero-web/ and https://hub.docker.com/r/jburel/omero-web-standalone