[Bug 1127570] New: No fish completion
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1127570
Bug ID: 1127570
Summary: No fish completion
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: yajo.sk8(a)gmail.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, vbatts(a)redhat.com
Description of problem:
Cannot use autocompletion whith fish shell
Version-Release number of selected component (if applicable):
fish-2.1.0-9.fc20.x86_64
docker-io-1.0.0-9.fc20.x86_64
How reproducible:
Write `docker [TAB]` using fish shell.
Actual results:
Shows directories in CWD.
Expected results:
attach events import load pull run tag
build export info login push save top
commit help insert logs restart search version
cp history inspect port rm start wait
diff images kill ps rmi stop
Additional info:
Current version of Docker provides it:
https://github.com/docker/docker/blob/v1.0.0/contrib/completion/fish/dock...
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 3 months
[Bug 1101123] New: docker package binary conflicts with docker-io
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1101123
Bug ID: 1101123
Summary: docker package binary conflicts with docker-io
Product: Fedora
Version: 20
Component: docker-io
Severity: medium
Assignee: lsm5(a)redhat.com
Reporter: dmcf(a)dcorking.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
There is a file name conflict for /usr/bin/docker between 2 Fedora 20 packages.
Version-Release number of selected component (if applicable):
docker-1.5-10.fc20.x86_64 (f20 updates, a dockapp that provides a system tray
for WindowMaker, XFCE etc.)
docker-io-0.11.1-1.fc20.x86_64.rpm (f20 updates, a new Linux containerization
app that has proven very popular)
How reproducible: Consistent.
Steps to Reproduce:
1. sudo yum install docker
2. sudo yum install docker-io
Actual results:
Transaction check error:
file /usr/bin/docker from install of docker-io-0.11.1-1.fc20.x86_64 conflicts
with file from package docker-1.5-10.fc20.x86_64
Expected results:
All packages in F20 should be able to co-exist unless a conflict is documented
in the RPM file.
Since the conflict is only file naming, one of these packages could be patched
to allow it to co-exist with the other.
Additional info:
Possible workaround that keeps docker working for me follows.
(It allows docker-io to install, but I am not sure if docker-io is fully
functioning.)
#!/bin/bash
sudo mv /usr/bin/docker /usr/bin/wmdocker
# user must change dock icons that link to docker to point to wmdocker
sudo yum install docker-io --downloadonly
cd /var/cache/yum/x86_64/20/updates/packages/
sudo rpm -Uvf --force docker-io-0.11.1-1.fc20.x86_64.rpm
The conflict probably also exists in rawhide. (unverified)
The upstream binary in both packages is 'docker'. Debian/Ubuntu rename their
binary to 'docker-io' to deal with the conflict.
There is a plan to replace the 'docker' package with a renamed 'wmdocker'
package in F21. (Bug # 1043676). However, that will take until F23 release to
complete the Obsoletes/Expires process. In the meantime, any user with docker
from F20 or rawhide will be unable to install docker-io, unless they use the
workaround.
Related issues:
* https://fedorahosted.org/fpc/ticket/341 "How to replace "docker" package with
an entirely different package of the same name?"
* https://bugzilla.redhat.com/show_bug.cgi?id=1043676 "drop docker from rawhide
(or redirect to wmdocker)"
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 3 months
[Bug 1114098] New: fedora 20: etcd broken on install, very out of date, and misconfigured.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1114098
Bug ID: 1114098
Summary: fedora 20: etcd broken on install, very out of date,
and misconfigured.
Product: Fedora
Version: 20
Component: etcd
Assignee: lacypret(a)gmail.com
Reporter: bugs(a)jameskyle.org
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lacypret(a)gmail.com,
lemenkov(a)gmail.com
Description of problem:
etcd service on fedora 20 only returns 404 page not found for all queries.
Version-Release number of selected component (if applicable):
Fedora 20, etcd 0.1.3
How reproducible:
100%
Steps to Reproduce:
1. yum install etcd
2. systemctl start etcd
3. curl http://127.0.0.1:4001/v2/keys/foo -d "Bar"
Actual results:
404 page not found
Expected results:
{"action":"set","node":{"key":"/message","value":"Hello","modifiedIndex":5,"createdIndex":5}}
Additional info:
The service was configured to use a systemd socket service, but (from the
systemd debs) "etcd doesn't have socket activation".
Even if I disabled the socket service and ran etcd 0.1.3 in the foreground with
defaults, the same behavior was manifest.
Installing the current 0.4.4 version of etcd produced the expected/desired
behavior.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1121100] New: allow docker run --net=none --hostname=....
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1121100
Bug ID: 1121100
Summary: allow docker run --net=none --hostname=....
Product: Fedora EPEL
Version: el6
Component: docker-io
Severity: medium
Assignee: lsm5(a)fedoraproject.org
Reporter: gilles.gouaillardet(a)gmail.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, vbatts(a)redhat.com
Currently, docker run will fail if both --net=none and --hostname=... options
are used.
This has been fixed in the docker git repository :
https://github.com/ggouaillardet/docker/commit/f411f8bfc5d04aed6499dfc90e...
could you please backport this fix to docker-io for epel-6 ?
Thanks and regards,
Gilles
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 5 months