stable

docker-1.13.1-42.git4402c09.fc27 and skopeo-0.1.25-2.git7fd6f66.fc27

FEDORA-2017-3da8ad596a created by lsm5 7 years ago for Fedora 27

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.

How to install

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

This update has been submitted for testing by lsm5.

7 years ago

This update has obsoleted skopeo-0.1.24-4.dev.git28d4e08.fc27, and has inherited its bugs and notes.

7 years ago

lsm5 edited this update.

New build(s):

  • docker-1.13.1-33.git790e958.fc27

Removed build(s):

  • docker-1.13.1-32.git790e958.fc27

Karma has been reset.

7 years ago

This update has been pushed to testing.

7 years ago
User Icon anonymous commented & provided feedback 7 years ago

Starting daemons fails with:

Oct 19 10:37:33 fedora systemd[1]: Starting Docker Application Container Engine...
Oct 19 10:37:34 fedora dockerd-current[2316]: time="2017-10-19T10:37:34+02:00" level=info msg="SUSE:secrets :: enabled"
Oct 19 10:37:34 fedora dockerd-current[2316]: Error starting daemon: opening seccomp profile (/etc/docker/seccomp.json) failed: open /etc/docker/seccomp.json: no such file or directory
Oct 19 10:37:34 fedora systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Oct 19 10:37:34 fedora systemd[1]: Failed to start Docker Application Container Engine.
Oct 19 10:37:34 fedora systemd[1]: docker.service: Unit entered failed state.
Oct 19 10:37:34 fedora systemd[1]: docker.service: Failed with result 'exit-code'.

karma: -1

User Icon lsm5 provided feedback 7 years ago

This update has been unpushed.

lsm5 edited this update.

New build(s):

  • docker-1.13.1-35.git8fd0ebb.fc27

Removed build(s):

  • docker-1.13.1-33.git790e958.fc27

Karma has been reset.

7 years ago

This update has been submitted for testing by lsm5.

7 years ago

lsm5 edited this update.

7 years ago
User Icon jmontleon commented & provided feedback 7 years ago
karma

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.

7 years ago

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.

7 years ago

This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes

7 years ago

lsm5 edited this update.

New build(s):

  • atomic-1.19.1-5.fc27
  • docker-1.13.1-37.git166a52e.fc27

Removed build(s):

  • docker-1.13.1-35.git8fd0ebb.fc27

Karma has been reset.

7 years ago

This update has been submitted for testing by lsm5.

7 years ago

This update has obsoleted atomic-1.19.1-4.fc27, and has inherited its bugs and notes.

7 years ago

lsm5 edited this update.

New build(s):

  • docker-1.13.1-38.git166a52e.fc27

Removed build(s):

  • docker-1.13.1-37.git166a52e.fc27

Karma has been reset.

7 years ago

This update has been pushed to testing.

7 years ago

lsm5 edited this update.

New build(s):

  • docker-1.13.1-40.git877b6df.fc27
  • atomic-1.19.1-6.fc27

Removed build(s):

  • atomic-1.19.1-5.fc27
  • docker-1.13.1-38.git166a52e.fc27
  • skopeo-0.1.24-6.dev.git28d4e08.fc27

Karma has been reset.

7 years ago

This update has been submitted for testing by lsm5.

7 years ago

This update has been pushed to testing.

7 years ago

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.

7 years ago

This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes

7 years ago

This update has been submitted for batched by lsm5.

7 years ago

This update has been submitted for stable by lsm5.

7 years ago

This update has been unpushed.

lsm5 edited this update.

New build(s):

  • docker-1.13.1-41.git0861eff.fc27

Removed build(s):

  • atomic-1.19.1-6.fc27
  • docker-1.13.1-40.git877b6df.fc27

Karma has been reset.

7 years ago

This update has been submitted for testing by lsm5.

7 years ago

lsm5 edited this update.

New build(s):

  • skopeo-0.1.25-2.git7fd6f66.fc27

Karma has been reset.

7 years ago
User Icon lsm5 commented & provided feedback 7 years ago

@phracek, please -1 the update for f26. This one is for f27

User Icon ttomecek commented & provided feedback 7 years ago

I installed these packages on my rawhide box, and openshift origin still can't run -- getting the same error as Petr mentioned above:

Error: failed to start container "deployment":
 Error response from daemon: {"message":"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/61474a7b-c854-11e7-a327-68f728aba37f/volumes/kubernetes.io~secret/deployer-token-frqln\\\\\\\" to
rootfs \\\\\\\"/var/lib/docker/overlay2/17772cead9f9fb1d52d6dc456a881cd6a828c8bb08bd91267805478a5732f29a/merged\\\\\\\" at \\\\\\\"/var/lib/docker/overlay2/17772cead9f9fb1d52
d6dc456a881cd6a828c8bb08bd91267805478a5732f29a/merged/run/secrets/kubernetes.io/serviceaccount\\\\\\\" caused \\\\\\\"mkdir /var/lib/docker/overlay2/17772cead9f9fb1d52d6dc456
a881cd6a828c8bb08bd91267805478a5732f29a/merged/run/secrets/kubernetes.io: read-only file system\\\\\\\"\\\"\"\n"}

This update has been pushed to testing.

7 years ago

lsm5 edited this update.

New build(s):

  • docker-1.13.1-42.git4402c09.fc27

Removed build(s):

  • docker-1.13.1-41.git0861eff.fc27

Karma has been reset.

7 years ago

This update has been submitted for testing by lsm5.

7 years ago

This update has been pushed to testing.

7 years ago

lsm5 edited this update.

7 years ago

lsm5 edited this update.

7 years ago
User Icon miabbott commented & provided feedback 7 years ago
karma

The docker daemon starts up successfully and you can (mostly) use it as normal. But BZ #1510139 still persists.

BZ#1504065 docker daemon failed to start (missing /etc/docker/seccomp.json)
BZ#1510139 Can't run systemd in non-privileged container
User Icon adelton commented & provided feedback 7 years ago
karma

I can now create pod and have container running with Kubernetes master again.

BZ#1504709 oc cluster up fails with secrets added to skopeo-containers
User Icon jonathancalloway commented & provided feedback 7 years ago
karma

Works for me

This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.

7 years ago

This update has been submitted for batched by lsm5.

7 years ago

This update has been submitted for stable by lsm5.

7 years ago

lsm5 edited this update.

7 years ago

This update has been pushed to stable.

7 years ago
User Icon anassahmed commented & provided feedback 7 years ago
karma

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


Please login to add feedback.

Metadata
Type
enhancement
Karma
2
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
disabled
Dates
submitted
7 years ago
in testing
7 years ago
in stable
7 years ago
modified
7 years ago
BZ#1478843 Package version 0.1.23-2.git1bbd87f has a file conflict with inn
0
0
BZ#1479003 skopeo-containers file conflict with inn
0
0
BZ#1504065 docker daemon failed to start (missing /etc/docker/seccomp.json)
0
1
BZ#1504709 oc cluster up fails with secrets added to skopeo-containers
0
1
BZ#1507679 Docker default registry change breaks many default behaviors including docker.com tutorial
0
0
BZ#1510139 Can't run systemd in non-privileged container
-1
0

Automated Test Results