martinpitt reported a new issue against the project: `releng` that you are following: `` Yesterday I noticed that https://registry.fedoraproject.org/ is missing an f28/cockpit container; the container git was grossly out of date indeed, so I [updated](https://src.fedoraproject.org/container/cockpit/commits/f28) it and did a [build](https://koji.fedoraproject.org/koji/buildinfo?buildID=1078705).
Now it's in the candidate registry: ``` repositories: candidate-registry.fedoraproject.org/f28/cockpit:f28-container-candidate-92075-20180502205553 candidate-registry.fedoraproject.org/f28/cockpit:0-1.f28container candidate-registry.fedoraproject.org/f28/cockpit:0 candidate-registry.fedoraproject.org/f28/cockpit:latest ```
I tested this on current Fedora Atomic: ``` # docker pull candidate-registry.fedoraproject.org/f28/cockpit:0-1.f28container # atomic install candidate-registry.fedoraproject.org/f28/cockpit:0-1.f28container # atomic run candidate-registry.fedoraproject.org/f28/cockpit:0-1.f28container ``` and I get a working Cockpit on https://127.0.0.1:9090.
Can you please publish this container?
Thank you! ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
mohanboddu added a new comment to an issue you are following: `` @cverna AFAIK we have to a full layered container images build/release.
Is that okay with you or do you think of any reason why we have to just do build/release just this layered image and if it is, how can we do this? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
cverna added a new comment to an issue you are following: `` Yeah so the next container release is schedule for Thursday 10 May. (Every 2 weeks). We could manually push this image or wait for next week. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
dustymabe added a new comment to an issue you are following: `` if possible let's go ahead and get this one out since they are looking to use it and promote f28 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
cverna added a new comment to an issue you are following: ``
if possible let's go ahead and get this one out since they are looking to use it and promote f28
+1 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
The status of the issue: `Please publish f28/cockpit container` of project: `releng` has been updated to: Closed as Fixed by mohanboddu.
mohanboddu added a new comment to an issue you are following: `` Okay, copied the images to registry.fp.o ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
martinpitt added a new comment to an issue you are following: `` I asked on #fedora-releng this morning and the answer was that it required filing a ticket. If container builds regularly happen anyway, that answers the question for the future, though, so thank you! Being out of date for a while isn't a problem, but not having a container image at all is.
I don't see the image on https://registry.fedoraproject.org/ yet, but I take it it just needs some time to propagate. Thanks everyone! ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
mohanboddu added a new comment to an issue you are following: `` @martinpitt Not sure about the web but
``` $ skopeo inspect docker://registry.fedoraproject.org/f28/cockpit:latest { "Name": "registry.fedoraproject.org/f28/cockpit", "Digest": "sha256:691df06defdc00cd72538b2c1232680b2610fbd51a1302bbfea7dbc26ba15b39", "RepoTags": [ "latest", "0", "0-1.f28container", "f28-container-candidate-92075-20180502205553" ], "Created": "2018-05-02T21:00:07.226612Z", "DockerVersion": "1.13.1", "Labels": { "Architecture": "x86_64", "BZComponent": "cockpit", "INSTALL": "/usr/bin/docker run --rm --privileged -v /:/host IMAGE /container/atomic-install", "Name": "f28/cockpit", "RUN": "/usr/bin/docker run -d --privileged --pid=host -v /:/host IMAGE /container/atomic-run --local-ssh", "Release": "1.f28container", "UNINSTALL": "/usr/bin/docker run --rm --privileged -v /:/host IMAGE /container/atomic-uninstall", "Version": "0", "architecture": "x86_64", "authoritative-source-url": "registry.fedoraproject.org", "build-date": "2018-05-02T20:55:59.724161", "com.redhat.build-host": "osbs-node01.phx2.fedoraproject.org", "com.redhat.component": "cockpit", "distribution-scope": "private", "install": "/usr/bin/docker run --rm --privileged -v /:/host IMAGE /container/atomic-install", "license": "MIT", "name": "f28/cockpit", "release": "1.f28container", "run": "/usr/bin/docker run -d --privileged --pid=host -v /:/host IMAGE /container/atomic-run --local-ssh", "uninstall": "/usr/bin/docker run --rm --privileged -v /:/host IMAGE /container/atomic-uninstall", "vcs-ref": "f19ffa7f365585deb680758f786cac091bc9c42d", "vcs-type": "git", "vendor": "Fedora Project", "version": "0" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:3a9b1fe8d365080aed52f1b4d20c22f8cbe41e68415588a4584f714018f86f81", "sha256:72d34b7122d499524c91c11749ff57dd5aa9efc138b522bf0d3e25566fd06887" ] } ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
cverna added a new comment to an issue you are following: ``
I don't see the image on https://registry.fedoraproject.org/ yet, but I take it it just needs some time to propagate. Thanks everyone!
If I am correct the website is regenerated every 6 hours by a cron job (it is a static web page). So it will take some time before it is updated. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
martinpitt added a new comment to an issue you are following: `` Indeed a docker pull works fine. Thanks! ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7483
rel-eng@lists.fedoraproject.org