Resolves: #1270521
built docker @rhatdan/fedora-1.8 commit#bdb52b6
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-2015-7e1a61e141
This update has been submitted for testing by lsm5.
This update has obsoleted docker-1.8.2-9.gitbdb52b6.fc23, and has inherited its bugs and notes.
I upgraded from the current version of docker in f23, ran a few hello world type containers, it works.
I installed this package on a clean install without docker, ran a busybox hello world container, worked.
I installed this package as an upgrade to docker currently available to an F23 system, ran a busybox hello world container, worked.
Couldn't replicate 1273893 by modifying install order, looking ok.
Booted F23 cloud image, installed latest docker, and then upgraded to this build.
Ran a few docker build, docker run, and docker stop operations without error.
docker build
docker run
docker stop
This update has been pushed to testing.
Looks good. Clean install and ran a few docker containers. I think the only difference is that now I see this when running docker logs:
[root@localhost ~]# docker logs 6dde625eb2c9 "logs" command is supported only for "json-file" logging driver (got: journald)
which I think is new. you can still see the logs with 'journalctl CONTAINER_ID=6dde625eb2c9`
Booted F23 cloud image, installed docker, then upgraded to this build.
I ran a number of docker build, docker run, and docker stop tasks without error
Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.
Ran a number of docker build and docker run tasks without error.
Ran a number of 'docker build' and 'docker run' tasks without error.
Booted F23 cloud image, installed docker, upgraded to this build.
Ran through a number of docker build, docker run, and docker stop tasks without error.
This update has been submitted for stable by lsm5.
This update has been pushed to stable.
This breaks kubernetes. In addition it breaks the Cockpit integration tests:
https://bugzilla.redhat.com/show_bug.cgi?id=1275593
https://github.com/cockpit-project/cockpit/issues/3156
I consider the "docker logs" regression found by dustymabe as serious.
Installing docker-selinux before docker still produces an error, but docker seems to work regardless.
We see the crashes mentioned by stef in our tests.
Please login to add feedback.
Confirm request to re-trigger tests.
This update has been submitted for testing by lsm5.
This update has obsoleted docker-1.8.2-9.gitbdb52b6.fc23, and has inherited its bugs and notes.
I upgraded from the current version of docker in f23, ran a few hello world type containers, it works.
I installed this package on a clean install without docker, ran a busybox hello world container, worked.
I installed this package as an upgrade to docker currently available to an F23 system, ran a busybox hello world container, worked.
Couldn't replicate 1273893 by modifying install order, looking ok.
Booted F23 cloud image, installed latest docker, and then upgraded to this build.
Ran a few
docker build,docker run, anddocker stopoperations without error.This update has been pushed to testing.
Looks good. Clean install and ran a few docker containers. I think the only difference is that now I see this when running docker logs:
which I think is new. you can still see the logs with 'journalctl CONTAINER_ID=6dde625eb2c9`
Booted F23 cloud image, installed docker, then upgraded to this build.
I ran a number of
docker build,docker run, anddocker stoptasks without errorLooks good. Clean install and ran a few docker containers. I think the only difference is that now I see this when running docker logs:
which I think is new. you can still see the logs with 'journalctl CONTAINER_ID=6dde625eb2c9`
Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.
Ran a number of
docker buildanddocker runtasks without error.Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.
Ran a number of 'docker build' and 'docker run' tasks without error.
Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.
Ran a number of
docker buildanddocker runtasks without error.Looks good. Clean install and ran a few docker containers. I think the only difference is that now I see this when running docker logs:
which I think is new. you can still see the logs with 'journalctl CONTAINER_ID=6dde625eb2c9`
Booted F23 cloud image, installed docker, upgraded to this build.
Ran through a number of
docker build,docker run, anddocker stoptasks without error.Looks good. Clean install and ran a few docker containers. I think the only difference is that now I see this when running docker logs:
which I think is new. you can still see the logs with 'journalctl CONTAINER_ID=6dde625eb2c9`
This update has been submitted for stable by lsm5.
This update has been pushed to stable.
This breaks kubernetes. In addition it breaks the Cockpit integration tests:
https://bugzilla.redhat.com/show_bug.cgi?id=1275593
https://github.com/cockpit-project/cockpit/issues/3156
I consider the "docker logs" regression found by dustymabe as serious.
Installing docker-selinux before docker still produces an error, but docker seems to work regardless.
We see the crashes mentioned by stef in our tests.