https://bugzilla.redhat.com/show_bug.cgi?id=1217987
Bug ID: 1217987
Summary: docker push to dockerhub does not work (docker 1.16)
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: spousty(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
I can build and tag a docker image on my local machine but I can not push it to
dockerhub. I am sure I have a dockerhub account and I can push with F20 and
docker 15. Maceij can push with Ubuntu and Docker 16.
Version-Release number of selected component (if applicable):
Docker version 1.6.0, build 3eac457/1.6.0
How reproducible:
Always
Steps to Reproduce:
1. Make a local docker image
2. Tag it
3. Try to push it to dockerhub
Actual results:
$ sudo docker build -t thesteve0/openshift-qpid:latest .
Sending build context to Docker daemon 2.048 kB
Sending build context to Docker daemon
Step 0 : FROM fedora/qpid
---> 6b45d8271e13
Step 1 : MAINTAINER spousty <spousty(a)redhat.com>
---> Using cache
---> 32b450b8f57a
Step 2 : ENV IMAGE_DESCRIPTION QPID C++ AMQP Server 0.30.3
---> Using cache
---> 03be2f186029
Step 3 : ENV IMAGE_TAGS qpid,qpid030,
---> Using cache
---> 13797654c23f
Step 4 : ENV IMAGE_EXPOSE_SERVICES 5672:qpid
---> Using cache
---> 3a0843e1e66e
Step 5 : EXPOSE 5672
---> Using cache
---> 465c93d05637
Step 6 : ENTRYPOINT qpidd -t --auth=no
---> Using cache
---> 4ff0b3679c09
Successfully built 4ff0b3679c09
$ sudo docker images
REPOSITORY TAG IMAGE ID
CREATED VIRTUAL SIZE
thesteve0/openshift-qpid latest 4ff0b3679c09 2
minutes ago 607.1 MB
$ sudo docker push thesteve0/openshift-qpid:latest
Do you really want to push to public registry? [Y/n]: Y
The push refers to a repository [docker.io/thesteve0/openshift-qpid] (len: 1)
FATA[0001] Repository does not exist: docker.io/thesteve0/openshift-qpid
Expected results:
The image should be pushed to dockerhub
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1214602
Bug ID: 1214602
Summary: Tracker for golang-github-docker-spdystream updates
Product: Fedora
Version: rawhide
Component: golang-github-gorilla-mux
Assignee: jchaloup(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-gorilla-mux for rawhide and other
fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1216151
Bug ID: 1216151
Summary: Docker fails mounting a volume as readonly on files
located under /usr
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: yann.robert(a)anantaplex.fr
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Docker fails to run a container with a volume on files located under /usr (or
on symbolic link to files located under /usr) if the ":ro" specification is
used to mount it as readonly
Version-Release number of selected component (if applicable):
docker-io-1.6.0-2.git3eac457.fc21.x86_64
How reproducible: 100%
Steps to Reproduce:
1. install docker package docker-io-1.6.0-2.git3eac457.fc21.x86_64
2. restart the docker service
3. run the following command
docker run -ti -v /etc/localtime:/etc/localtime:ro busybox echo hello
Actual results:
get exit code 1
and message FATA[0000] Error response from daemon: Cannot start container
4bb87515e4eb828b295eb4718a7159c958a1154ed839b29fd213a597b91a200e: [8] System
error: Relabeling content in /usr is not allowed.
Expected results:
get exit code 0
and message "hello"
Additional info:
please refer to initial bug report on docker repository at github
https://github.com/docker/docker/issues/12811
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1176302
Bug ID: 1176302
Summary: /var/log/docker incorrectly asserts that kernel
2.6.32* "might be unstable running docker"
Product: Fedora EPEL
Version: el6
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: afoxson(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Description of problem:
The following warning appears in /var/log/docker:
"WARNING: You are running linux kernel version 2.6.32-504.1.3.el6.x86_64, which
might be unstable running docker. Please upgrade your kernel to 3.8.0."
Version-Release number of selected component (if applicable):
docker-io-1.3.2-2.el6.x86_64.rpm
How reproducible:
Consistently.
Steps to Reproduce:
1. Run docker in daemon mode.
2. Review /var/log/docker.
Actual results:
The aforementioned warning appears in /var/log/docker.
Expected results:
The aforementioned warning not appearing in /var/log/docker.
Additional info:
This warning is incorrect as per:
https://github.com/docker/docker/issues/407#issuecomment-43206662
which states:
"Kernels older than 3.8 aren't supported. That means technical support isn't
provided and you might run into unexpected behavior, even if it seems like it's
working. The only exception is the kernel provided by RHEL6 (2.6.32xxxxxx)
which was patched and improved to work properly with Docker."
It seems that an environment variable is available for this situation, as per:
https://github.com/shykes/docker-dev/commit/2c2a655da14f6de9353454673f2a1c9…
which states:
"set DOCKER_NOWARN_KERNEL_VERSION=1 to disable the warning for RHEL 6.5"
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1213258
Bug ID: 1213258
Summary: Docker 1.6 needs tar but does not require it
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: jpazdziora(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Starting container fails with fork/exec /usr/bin/tar: no such file or directory
Version-Release number of selected component (if applicable):
docker-io-1.6.0-0.1.rc6.fc21
How reproducible:
Seen once, assume deterministic.
Steps to Reproduce:
1. Build an image.
2. Run a container.
Actual results:
time="2015-04-20T03:35:12-04:00" level=fatal msg="Error response from daemon:
Cannot start container
4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29: [8] System
error: [/usr/bin/tar -cf
/var/lib/docker/tmp/4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29725221613/_run.tar
-C
/var/lib/docker/devicemapper/mnt/4df4e127d80dbfbf26a972a00f51085570fff275554979e80901ee93c7f69b29/rootfs/run
.] failed: : fork/exec /usr/bin/tar: no such file or directory"
Expected results:
No error, container runs.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1219703
Bug ID: 1219703
Summary: CVE-2015-3629 docker-io: docker: symlink traversal on
container respawn allows local privilege escalation
[fedora-all]
Product: Fedora
Version: 21
Component: docker-io
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ichavero(a)redhat.com
Reporter: tjay(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1219058 (CVE-2015-3629)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1219058
[Bug 1219058] CVE-2015-3629 docker: symlink traversal on container respawn
allows local privilege escalation
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1219707
Bug ID: 1219707
Summary: CVE-2015-3627 docker-io: docker: insecure opening of
file-descriptor 1 leading to privilege escalation
[fedora-all]
Product: Fedora
Version: 21
Component: docker-io
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ichavero(a)redhat.com
Reporter: tjay(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1219061 (CVE-2015-3627)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1219061
[Bug 1219061] CVE-2015-3627 docker: insecure opening of file-descriptor 1
leading to privilege escalation
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1219711
Bug ID: 1219711
Summary: CVE-2015-3630 docker-io: docker: Read/write proc paths
allow host modification & information disclosure
[fedora-all]
Product: Fedora
Version: 21
Component: docker-io
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ichavero(a)redhat.com
Reporter: tjay(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1219063 (CVE-2015-3630)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1219063
[Bug 1219063] CVE-2015-3630 docker: Read/write proc paths allow host
modification & information disclosure
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1219715
Bug ID: 1219715
Summary: CVE-2015-3631 docker-io: docker: volume mounts allow
LSM profile escalation [fedora-all]
Product: Fedora
Version: 21
Component: docker-io
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ichavero(a)redhat.com
Reporter: tjay(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1219065 (CVE-2015-3631)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1219065
[Bug 1219065] CVE-2015-3631 docker: volume mounts allow LSM profile
escalation
--
You are receiving this mail because:
You are on the CC list for the bug.