move rhel secrets info from docker to skopeo-containers
Add override kernel check.
built commit 28d4e08
Addition of remediate
New atomic and registries code
Addition of run for system containers
remove skopeo build from update since 0.1.24-7 is already set to move to stable.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2017-3da8ad596a
Please login to add feedback.
This update has been submitted for testing by lsm5.
This update has obsoleted skopeo-0.1.24-4.dev.git28d4e08.fc27, and has inherited its bugs and notes.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been pushed to testing.
Starting daemons fails with:
karma: -1
This update has been unpushed.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsm5.
lsm5 edited this update.
I am getting errors that I believe are coming from the skopeo update when running oc cluster up.
With skopeo-containers-0.1.24-6.dev.git28d4e08.fc27.x86_64 I am seeing errors like below. I can upgrade to this version and restart docker to break it and downgrade to skopeo-containers-0.1.24-4.dev.git28d4e08.fc27.x86_64 and restart docker to fix it at will.
"dockerd-current[21575]: time="2017-10-19T14:38:59.520129615-04:00" level=error msg="Handler for POST /v1.26/containers/14a6af3ee85b702c4cbd6d768e91131a58a1d0c028b65ff615f4ed5409e3682d/start returned error: oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:364: container init caused \\"rootfs_linux.go:54: mounting \\\\"/var/lib/origin/openshift.local.volumes/pods/c31e982d-b4fc-11e7-8a8c-64006a559656/volumes/kubernetes.io~secret/pvinstaller-token-r2q5c\\\\" to rootfs \\\\"/var/lib/docker/devicemapper/mnt/79e13fe00b5c35629c2f2c4e03b0c6a9825e384ffecc052d01689ab656443d01/rootfs\\\\" at \\\\"/var/lib/docker/devicemapper/mnt/79e13fe00b5c35629c2f2c4e03b0c6a9825e384ffecc052d01689ab656443d01/rootfs/run/secrets/kubernetes.io/serviceaccount\\\\" caused \\\\"mkdir /var/lib/docker/devicemapper/mnt/79e13fe00b5c35629c2f2c4e03b0c6a9825e384ffecc052d01689ab656443d01/rootfs/run/secrets/kubernetes.io: read-only file system\\\\"\\"\"\n" ```
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsm5.
This update has obsoleted atomic-1.19.1-4.fc27, and has inherited its bugs and notes.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been pushed to testing.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsm5.
This update has been pushed to testing.
I have similiar problem like https://bodhi.fedoraproject.org/users/jmontleon See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1511375
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for batched by lsm5.
This update has been submitted for stable by lsm5.
This update has been unpushed.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsm5.
lsm5 edited this update.
New build(s):
Karma has been reset.
@phracek, please -1 the update for f26. This one is for f27
I installed these packages on my rawhide box, and openshift origin still can't run -- getting the same error as Petr mentioned above:
This update has been pushed to testing.
lsm5 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsm5.
This update has been pushed to testing.
lsm5 edited this update.
lsm5 edited this update.
The
docker
daemon starts up successfully and you can (mostly) use it as normal. But BZ #1510139 still persists.I can now create pod and have container running with Kubernetes master again.
Works for me
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has been submitted for batched by lsm5.
This update has been submitted for stable by lsm5.
lsm5 edited this update.
This update has been pushed to stable.
Problem: cannot install the best update candidate for package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
- nothing provides atomic-registries >= 1.19.1-6 needed by docker-2:1.13.1-42.git4402c09.fc27.x86_64