https://bugzilla.redhat.com/show_bug.cgi?id=1145660
Bug ID: 1145660
Summary: [PATCH] Support /etc/sysconfig/docker-storage
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: walters(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Created attachment 940423
--> https://bugzilla.redhat.com/attachment.cgi?id=940423&action=edit
[PATCH] Support /etc/sysconfig/docker-storage
This will allow installation programs to pre-configure storage easily.
It will be used by Atomic to set up Docker for direct LVM.
---
docker-storage.sysconfig | 14 ++++++++++++++
docker.service | 3 ++-
docker.spec | 5 ++++-
3 files changed, 20 insertions(+), 2 deletions(-)
create mode 100644 docker-storage.sysconfig
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1149882
Bug ID: 1149882
Summary: docker socket not found errors
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: bparees(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
When run as a service, I frequently run into issues with the
/var/run/docker.sock being reported as not found, but if i shutdown the
service, remove /var/run/docker.sock, and run "docker -d" manually instead, I
have no such problem.
In addition, systemctl start docker does not appear to consistently create
/var/run/docker.sock, though the docker daemon reports as running.
Version-Release number of selected component (if applicable):
docker-io-1.2.0-2.fc20.x86_64
How reproducible:
Intermittent, most consistently recreates when bind mounting the docker socket
into a docker container and trying to perform docker operations from within
that container.
Additional info:
Disabling selinux has no effect on the results.
Sample output:
running as a service:
[bparees@bparees ~]$ ps ax | grep docker
10731 ? Ssl 0:00 /usr/bin/docker -d -H fd:// --selinux-enabled
11021 pts/6 S+ 0:00 grep --color=auto docker
[bparees@bparees ~]$ ls -l /var/run/docker*
-rw-r--r--. 1 root root 5 Oct 6 16:08 /var/run/docker.pid
[bparees@bparees ~]$ docker ps
2014/10/06 16:10:03 Get http:///var/run/docker.sock/v1.14/containers/json: dial
unix /var/run/docker.sock: no such file or directory
restarting manually:
[bparees@bparees ~]$ sudo systemctl stop docker
[sudo] password for bparees:
Warning: Stopping docker, but it can still be activated by:
docker.socket
[bparees@bparees ~]$ sudo docker -d >& /tmp/out &
[1] 11343
[bparees@bparees ~]$ ls -l /var/run/docker.*
-rw-r--r--. 1 root root 5 Oct 6 16:10 /var/run/docker.pid
srw-rw----. 1 root docker 0 Oct 6 16:10 /var/run/docker.sock
[bparees@bparees ~]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1047194
Bug ID: 1047194
Summary: etcd-0.2.0 is available
Product: Fedora
Version: rawhide
Component: etcd
Keywords: FutureFeature, Triaged
Assignee: lacypret(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lacypret(a)gmail.com,
lemenkov(a)gmail.com, lsm5(a)redhat.com
Latest upstream release: 0.2.0
Current version/release in Fedora Rawhide: 0.1.2-5.fc21
URL: https://api.github.com/repos/coreos/etcd/tags
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
--
You are receiving this mail because:
You are on the CC list for the bug.
Summary of changes:
c0f88ed... Resolves: rhbz#1156492 - initial upload (*)
6598679... expand arches instead of go_arches (*)
(*) This commit already existed in another branch; no separate mail sent