[Bug 1037830] New: Error pulling image, Authentication is required / Server error: 404
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1037830
Bug ID: 1037830
Summary: Error pulling image, Authentication is required /
Server error: 404
Product: Fedora EPEL
Version: el6
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: jeckersb(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Version-Release number of selected component (if applicable):
docker-io-0.7.0-14.el6.x86_64
Red Hat Enterprise Linux Server release 6.5 (Santiago)
How reproducible:
Always
Steps to Reproduce:
1. Run `docker -d -b none -D`
2. In another terminal, run `docker pull mattdm/fedora`
Actual results:
# docker pull mattdm/fedora
Pulling repository mattdm/fedora
1bdd590de956: Error pulling image (f20) from mattdm/fedora, Authentication is
required.
64e0619c473e: Error pulling image (latest) from mattdm/fedora, Authentication
is required.
97fc5bf7f8d4: Error pulling image (f20rc3.small) from mattdm/fedora,
Authentication is required.
a567e6f3d26a: Error pulling image (f19) from mattdm/fedora, Authentication is
required.
2013/12/03 21:15:36 Server error: 404 trying to fetch remote history for
mattdm/fedora
Expected results:
(Taken from my F20 system which works perfectly)
# docker pull mattdm/fedora
Pulling repository mattdm/fedora
1bdd590de956: Download complete
a567e6f3d26a: Download complete
64e0619c473e: Download complete
97fc5bf7f8d4: Download complete
Additional info:
There doesn't seem to be anything useful in the daemon output by default. I've
added debug statements in various places to try and understand what's going on.
I'll elaborate in future comments when I can better organize what I'm seeing.
Just wanted to get this out there incase it's something obvious :)
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1038329] New: Updating docker-io should probably restart the daemon
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1038329
Bug ID: 1038329
Summary: Updating docker-io should probably restart the daemon
Product: Fedora
Version: 19
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: luto(a)mit.edu
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
vbatts(a)redhat.com
I upgraded docker-io and, after the upgrade, I got errors about missing
dockerinit. systemctl restart docker fixed it.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1045173] New: Accessing Docker containers from outside network - adding firewall exceptions problem
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1045173
Bug ID: 1045173
Summary: Accessing Docker containers from outside network -
adding firewall exceptions problem
Product: Fedora EPEL
Version: el6
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: ajinkya(a)ajinkyakulkarni.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
skottler(a)redhat.com, vbatts(a)redhat.com
I am using Docker 0.7.0 to create containers on RedHat Enterprise Linux 6.5.
When firewall is turned off containers can talk to outside world, but when
firewall is on, container cannot be accessed from outside.
This is how I am running the docker and mapping a port from host to container
$ docker run -i -t -p 3838:3838 shiny "shiny-server"
Without firewall, I can access Node.js server running inside a container on
port 3838 from outside network as http://servername:3838, but not with firewall
turned on.
These are my default firewall rules –
==============================================
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
==============================================
I have tried opening a port 3838 by adding a rule as below, but it does not
work
-A INPUT -m state --state NEW -m tcp -p tcp --dport 3838 -j ACCEPT
Docker is creating a virtual NAT on the host machine, I am feeling that somehow
firewall is blocking the packet forwarding from eth0 to docker 0
This is the output of $ifconfig (I have masked the server IP)
docker0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: fe80::87d:8dff:fed0:f16d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:408321 errors:0 dropped:0 overruns:0 frame:0
TX packets:681809 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:126511933 (120.6 MiB) TX bytes:924200959 (881.3 MiB)
eth0 Link encap:Ethernet HWaddr 00:25:64:A8:5B:8F
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.240.0
inet6 addr: XXXX::XXX:XXXX:XXXX:XXXX/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29786186 errors:0 dropped:0 overruns:0 frame:0
TX packets:1137982 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4209047011 (3.9 GiB) TX bytes:234657696 (223.7 MiB)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8444 errors:0 dropped:0 overruns:0 frame:0
TX packets:8444 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4701771 (4.4 MiB) TX bytes:4701771 (4.4 MiB)
Output of $docker version :
Client version: 0.7.0
Go version (client): go1.1.2
Git commit (client): 0ff9bc1/0.7.0
Server version: 0.7.0
Git commit (server): 0ff9bc1/0.7.0
Go version (server): go1.1.2
Last stable version: 0.7.2, please update docker
Output of $docker info:
Containers: 321
Images: 278
Driver: devicemapper
Pool Name: docker-8:17-13239310-pool
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 56464.5 Mb
Data Space Total: 102400.0 Mb
Metadata Space Used: 59.5 Mb
Metadata Space Total: 2048.0 Mb
I need help in making docker containers accessible from outside network without
turning off the entire firewall.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1041400] New: docker permission denied errors
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1041400
Bug ID: 1041400
Summary: docker permission denied errors
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
rest api calls seem to fail for docker on rawhide
Version-Release number of selected component (if applicable): 0.7.1 (both rpm
and binary released by upstream)
How reproducible: consistent
Steps to Reproduce:
1. install docker-io (via yum or upstream binary)
2. try 'docker search' / 'docker pull' / 'docker login' or anything else
Actual results:
$ sudo docker search fedora
2013/12/12 09:43:53 Error: Get https://index.docker.io/v1/search?q=fedora: dial
tcp 54.234.135.251:443: permission denied
Expected results:
should show a list of fedora images
Additional info: I didn't find this in f19 or epel (only on rawhide)
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1057340] New: rpm macros for golang
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1057340
Bug ID: 1057340
Summary: rpm macros for golang
Product: Fedora
Version: rawhide
Component: golang
Severity: low
Assignee: adam(a)spicenitz.org
Reporter: vbatts(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adam(a)spicenitz.org, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
lsm5(a)redhat.com, renich(a)woralelandia.com,
skottler(a)redhat.com, vbatts(a)redhat.com
include in the golang rpm an /etc/rpm/macros.golang for defining %gopath such
that it is a system definition.
There may be other rpm automations to add as well. Ideally a post script for
__spec_install_post that could produce Provides: and Requires: of the golang()
libraries exported and imported.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1059743] New: bad filenames in rpm scriptlets expanded
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1059743
Bug ID: 1059743
Summary: bad filenames in rpm scriptlets expanded
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: jorton(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
skottler(a)redhat.com, vbatts(a)redhat.com
Description of problem:
# rpm -q --scripts docker-io | grep systemctl
/usr/bin/systemctl preset /builddir/build/SOURCES/docker.service
>/dev/null 2>&1 || :
/usr/bin/systemctl --no-reload disable
/builddir/build/SOURCES/docker.service > /dev/null 2>&1 || :
/usr/bin/systemctl stop /builddir/build/SOURCES/docker.service >
/dev/null 2>&1 || :
/usr/bin/systemctl daemon-reload >/dev/null 2>&1 || :
/usr/bin/systemctl try-restart /builddir/build/SOURCES/docker.service
>/dev/null 2>&1 || :
Version-Release number of selected component (if applicable):
docker-io-0.7.6-4.fc20.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1046882] New: docker-io: Make it available for EPEL 7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1046882
Bug ID: 1046882
Summary: docker-io: Make it available for EPEL 7
Product: Fedora EPEL
Version: el7
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: mgoldman(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
skottler(a)redhat.com, vbatts(a)redhat.com
Description of problem:
RHEL 7 beta was released, we need to make docker-io available in EPEL 7.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months
[Bug 1048775] New: invalid key/value pair in /etc/udev/rules.d/80-docker.rules
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1048775
Bug ID: 1048775
Summary: invalid key/value pair in
/etc/udev/rules.d/80-docker.rules
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: m.a.young(a)durham.ac.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
skottler(a)redhat.com, vbatts(a)redhat.com
I am getting warnings like
Jan 6 10:10:01 myhostname systemd-udevd: invalid key/value pair in file
/etc/udev/rules.d/80-docker.rules on line 2,starting at character 138 ('\"')
in /var/log/messages. I think this is due to a missing quote in
80-docker.rules, and the line
SUBSYSTEM=="block", DEVPATH=="/devices/virtual/block/loop*",
ATTR{loop/backing_file}=="/var/lib/docker/*, ENV{UDISKS_PRESENTATION_HIDE}="1",
ENV{UDISKS_IGNORE}="1"
should be
SUBSYSTEM=="block", DEVPATH=="/devices/virtual/block/loop*",
ATTR{loop/backing_file}=="/var/lib/docker/*",
ENV{UDISKS_PRESENTATION_HIDE}="1", ENV{UDISKS_IGNORE}="1"
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months