profile
viewpoint

andrewhsu/docker-linux-pkg 1

POC for docker linux packaging

andrewhsu/andrewhsu.github.io 0

:bowtie: public website

andrewhsu/azure-container-networking-1 0

Azure Container Networking Plugins for Linux and Windows Containers

andrewhsu/benchmarks 0

Benchmarks for the perf dashboard

andrewhsu/buildkit 0

concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit

andrewhsu/calico-1 0

Cloud native application connectivity and network policy

andrewhsu/centos7-yum 0

Make minimal centos7 image with just yum

andrewhsu/chef-cookbooks-docker 0

Chef Cookbook for Docker

andrewhsu/cli 0

The Docker CLI

andrewhsu/compose 0

Define and run multi-container applications with Docker

fork andrewhsu/opentelemetry-js

OpenTelemetry API for Javascript (both Node and browser)

https://opentelemetry.io

fork in 3 days

issue commentopen-telemetry/opentelemetry-go

Update README.md

I'll take this one.

MrAlias

comment created time in 9 days

issue openedopen-telemetry/community

guidance for multiple repos per SIG

After attending a few SIGs, I've observed a common pattern that seems to cause pause in getting code changes into the project: committing auxiliary code to the SIG SDK repo, e.g. code for plugins and code for auto-instrumentation.

The debate usually revolves around keeping a mono-repo structure vs creating lots of separate repos for each plugin (could be 10s of plugins), and varying degrees of structure in-between.

I'd like to propose the open-telemetry adopt an option to create multiple repo structure to allow SIGs chose within their community if they need more than 1 repo and have it created quickly, but with some guide rails. A guidance along the lines of these points:

  • SIGs may have 1 main repo for their codebase and it must be listed in the top-level list of SIGs https://github.com/open-telemetry/community#special-interest-groups as well as the registry https://opentelemetry.io/registry/
  • SIGs may choose to have an auxiliary repo to keep other code, but it must have a repo name prefix the same as their main repo. The main repo should point to the auxiliary repo in their readme and also list the auxiliary repo in the registry. The SIG should be mindful of having PR checks in the auxiliary repo verify code is compatible with the main repo.
  • SIGs may also chose to have a policy of externally-related repos (repos not in the open-telemetry github org) to associate with and if so state in the readme of the main repo to add a pointer to the externally-related repo in the registry. There should also be documentation on how to make sure the externally-related repo is kept up-to-date with the SIG's main repo codebase for PR checks.
  • In general it would be good to keep the number of auxiliary repos to a minimum (say less than 5) so as to limit the administrative process of maintaining too many repos for open-telemetry.

My hope is this guidance will help SIGs come to resolution quickly about adopting code.

created time in 9 days

issue commentopen-telemetry/opentelemetry-go

Document open-tracing to open-telemetry migration path.

@daixiang0 in regards to your desire to move OpenTracing to OpenTelemetry, the opentelemetry-go project is based on the specification work that is ongoing in opentelemetry-specification and there is still a bit of work to get the specification to 1.0 release so opentelemetry-go can fully implement. Here is a list of the milestones set back in October 2019 for the specification which should give you an idea of the roadmap: https://github.com/open-telemetry/opentelemetry-specification/blob/a131ae1ccabee8cc8f3b8cf109b81be378006fea/milestones.md

Speaking just for LightStep, there is also a bit of work that needs to be done before the work put into opentelemetry-go is ready for customers and we're actively planning for this as the specification rolls along.

daixiang0

comment created time in 16 days

issue commentopen-telemetry/opentelemetry-js

Node 8 Build fails

I see that Node.js 8 stopped maintenance in January 2020 https://nodejs.org/en/about/releases/

Is it still desirable to support? (I admit I'm not in touch with the user base of Node.js 8 so forgive this naive question)

dyladan

comment created time in 17 days

delete branch andrewhsu/lightstep-tracer-go

delete branch : fix-readme-onevent

delete time in 2 months

PR opened lightstep/lightstep-tracer-go

update README.md to replace mention of OnEvent

The OnEvent function is deprecated, use SetGlobalEventHandler instead.

Follow up to PR #158 Related issue #157

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchandrewhsu/lightstep-tracer-go

branch : fix-readme-onevent

created branch time in 2 months

fork andrewhsu/lightstep-tracer-go

The LightStep distributed tracing library for Go

http://lightstep.com

fork in 2 months

delete branch andrewhsu/docker-ce

delete branch : 1903ga

delete time in 3 months

push eventdocker/docker-ce

Andrew Hsu

commit sha cd61b7839661971a12f62f1f2747020d18c1480f

bump ver 19.03.5 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

Andrew Hsu

commit sha 633a0ea838f10e000b7c6d6eed1623e6e988b5bb

Merge pull request #637 from andrewhsu/1903ga [19.03] bump ver 19.03.5

view details

push time in 3 months

PR merged docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5

bump ver

+3 -2

1 comment

2 changed files

andrewhsu

pr closed time in 3 months

pull request commentdocker/docker-ce

[19.03] bump ver 19.03.5

Merging to get builds going.

andrewhsu

comment created time in 3 months

push eventandrewhsu/docker-ce

Tonis Tiigi

commit sha 44aa687b7e55dbe338b70a6af38c3a21cc2ed69d

vendor: update buildkit to 928f3b48 Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Upstream-commit: 33b2719488ec44196846ef61c4887a784edca081 Component: engine

view details

Andrew Hsu

commit sha 78173b207025733b91599a3ea9a5ef365fd956be

Merge pull request #422 from tonistiigi/1903-update-buildkit [19.03] vendor: update buildkit to 928f3b48 Upstream-commit: ea84732a77251e0d7af278e2b7df1d6a59fca46b Component: engine

view details

GordonTheTurtle

commit sha 50c71c735cdd28bc437d8f99694034f816fd1a45

Merge component 'engine' from git@github.com:docker/engine 19.03

view details

Andrew Hsu

commit sha cd61b7839661971a12f62f1f2747020d18c1480f

bump ver 19.03.5 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 3 months

startedlucas-clemente/quic-go

started time in 3 months

push eventandrewhsu/docker-ce

Andrew Hsu

commit sha 1eef12cea9d4ead0348c0174f682f15911694faa

bump ver 19.03.5 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 3 months

push eventdocker/engine

Tonis Tiigi

commit sha 33b2719488ec44196846ef61c4887a784edca081

vendor: update buildkit to 928f3b48 Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

view details

Andrew Hsu

commit sha ea84732a77251e0d7af278e2b7df1d6a59fca46b

Merge pull request #422 from tonistiigi/1903-update-buildkit [19.03] vendor: update buildkit to 928f3b48

view details

push time in 3 months

PR merged docker/engine

[19.03] vendor: update buildkit to 928f3b48 impact/changelog

Brings in: https://github.com/moby/buildkit/pull/1257 cache: fix possible concurrent maps write on parent release

Signed-off-by: Tonis Tiigi tonistiigi@gmail.com

+5 -7

0 comment

2 changed files

tonistiigi

pr closed time in 3 months

PR opened docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5

bump ver

+2 -2

0 comment

2 changed files

pr created time in 3 months

create barnchandrewhsu/docker-ce

branch : 1903ga

created branch time in 3 months

delete branch andrewhsu/docker-ce

delete branch : 1903b1

delete time in 3 months

issue commentdocker/for-linux

dockerd: high memory usage

@ceecko could you provide steps to reproduce? With current description of the issue, hard to nail down what is happening on your system.

ceecko

comment created time in 3 months

issue closeddocker/for-linux

Upload gpg key to keyservers

<!-- This issue tracker is for bug reports and feature requests. For questions, and getting help on using docker:

  • Docker documentation - https://docs.docker.com
  • Docker Forums - https://forums.docker.com
  • Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
  • Post a question on StackOverflow, using the Docker tag -->
  • [] This is a bug report
  • [x ] This is a feature request
  • [ ] I searched existing issues before opening this one

<!-- DO NOT report security issues publicly! If you suspect you discovered a security issue, send your report privately to security@docker.com. --> Hi,

Can the docker team please upload their gpg public key to a keyserver to facilitate its users in cross-checking the validity of the key when importing it for the first-time?

I downloaded the docker gpg key from the following URL:

  • https://download.docker.com/linux/centos/gpg

That gave me a key with fingerprint 060A 61C5 1B55 8A7F 742B 77AA C52F EB6B 621E 9F35 and a uid for docker@docker.com

user@personal:~$ gpg --list-keys docker
pub   rsa4096/0xC52FEB6B621E9F35 2017-02-22 [SCEA]
      Key fingerprint = 060A 61C5 1B55 8A7F 742B  77AA C52F EB6B 621E 9F35
uid                   [ unknown] Docker Release (CE rpm) <docker@docker.com>

user@personal:~$ 

But then I went to validate that this key was indeed correct, and I was stunned to find that it isn't listed on the sks keyservers or the better/replacement keyserver https://keys.openpgp.org/

  • https://keys.openpgp.org/search?q=docker%40docker.com

Moreover, there's no non-self signatures on the key

user@disp4086:~$ curl  --tlsv1.2 --proto =https --location https://download.docker.com/linux/centos/gpg > docker.gpg
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1627  100  1627    0     0    668      0  0:00:02  0:00:02 --:--:--   668
user@disp4086:~$ cat docker.gpg | gpg --list-packets
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
# off=0 ctb=99 tag=6 hlen=3 plen=525
:public key packet:
	version 4, algo 1, created 1487791233, expires 0
	pkey[0]: [4096 bits]
	pkey[1]: [17 bits]
	keyid: C52FEB6B621E9F35
# off=528 ctb=b4 tag=13 hlen=2 plen=43
:user ID packet: "Docker Release (CE rpm) <docker@docker.com>"
# off=573 ctb=89 tag=2 hlen=3 plen=567
:signature packet: algo 1, keyid C52FEB6B621E9F35
	version 4, created 1487792760, md5len 0, sigclass 0x13
	digest algo 10, begin of digest e8 2d
	hashed subpkt 2 len 4 (sig created 2017-02-22)
	hashed subpkt 27 len 1 (key flags: 2F)
	hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 3)
	hashed subpkt 21 len 4 (pref-hash-algos: 10 9 8 11)
	hashed subpkt 22 len 4 (pref-zip-algos: 2 3 1 0)
	hashed subpkt 30 len 1 (features: 01)
	hashed subpkt 23 len 1 (keyserver preferences: 80)
	subpkt 16 len 8 (issuer key ID C52FEB6B621E9F35)
	data: [4094 bits]
user@disp4086:~$ 

In-case it isn't clear, there's significant security risks with the X.509 security model used by my browser (or curl, etc) when downloading the docker gpg key from https://download.docker.com/linux/centos/gpg. HSTS is great when re-visiting a website, but the first time I visit docker.com, it wouldn't be too difficult for a malicious actor to MITM the connection with a cert signed by the extremely large list of CAs trusted by popular browsers -- which includes, for example, organizations controlled by State Actors who have a history of human rights abuses. And, historically, included many CAs that had to be removed because the CA's private key was stolen or was otherwise signing certificates that they shouldn't have been. If any cert is signed by any of those CAs, a MITM actor can send the wrong gpg key to a client, and the browser will show no indication of wrong-doing.

As suggested above, the solution to this problem is:

  1. publishing the docker public key on other domains in addition to docker.com, such as the keys.openpgp.org keyserver

  2. signing your public key with other gpg keys that are well integrated in the web of trust

The second item is a more complicated and long-term solution, so this issue is a feature request to upload the docker gpg key to the keys.openpgp.org keyserer, which should only take a few minutes to do. You'll need to click a link sent to the uid of the key (docker@docker.com) as described here https://keys.openpgp.org/about

closed time in 3 months

maltfield

issue commentdocker/for-linux

Upload gpg key to keyservers

Closing as duplicate of #602

maltfield

comment created time in 3 months

issue commentdocker/for-linux

Upload gpg key to keyservers

cc @justincormack

maltfield

comment created time in 3 months

issue commentdocker/for-linux

failed to add interface

@xupyp1 can you provide the commands you ran to get the error?

xupyp1

comment created time in 3 months

startedzmb3/spotify

started time in 3 months

startedgoproxy/goproxy

started time in 3 months

pull request commentmoby/moby

Fix docker crash when creating namespaces with UID in /etc/subuid and /etc/subgid

needs a rebase to get the new jenkinsfile to run today's PR checks. triggering of old jenkins job will not work anymore

yongtang

comment created time in 4 months

pull request commentmoby/moby

Windows: Build and use gotestsum for running all tests

This PR is valuable as is with RS5 junit test results in jenkins. It is important to expose the failures since the return code is always success.

I'd recommend getting this PR in as soon as possible and having a separate PR for RS1.

thaJeztah

comment created time in 4 months

delete branch andrewhsu/docker-ce

delete branch : 1903rc1

delete time in 4 months

push eventdocker/docker-ce

Andrew Hsu

commit sha 074ef5074a8807932b5ed6b14cce28dd1a156ab5

bump ver 19.03.5-rc1 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

Andrew Hsu

commit sha 3e4013245a8c13679ea3fb84e03490b439e99490

Merge pull request #636 from andrewhsu/1903rc1 [19.03] bump ver 19.03.5-rc1

view details

push time in 4 months

PR merged docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-rc1

bump ver

+2 -1

1 comment

2 changed files

andrewhsu

pr closed time in 4 months

pull request commentdocker/docker-ce

[19.03] bump ver 19.03.5-rc1

Merging to get builds going.

andrewhsu

comment created time in 4 months

push eventandrewhsu/docker-ce

Sebastiaan van Stijn

commit sha 6c02751cecabf6ec4f39d3ddc62c1ebc6c01be17

Revert "Revert "[19.03] bump swarmkit to f35d9100f2c6ac810cc8d7de6e8f93dcc7a42d29"" This reverts commit ef4366ee890abc587b291f7e41223a2c51e14153. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 0c38d56a6dae8c9c8379d29083b759005308ebc9 Component: engine

view details

Arko Dasgupta

commit sha a53e379675d6aec789ad4b54194bb33bb649a1fb

Add TC to check dyanmic subnet for ingress network Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com> (cherry picked from commit e2b5ac75a393f6942c37efdd888fc3bc761de244) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 12e7d99439917b44a173e5326798365870bbbc90 Component: engine

view details

Andrew Hsu

commit sha 41236fe25e43660ac3d84fea558dd5fe8083d0a3

Merge pull request #374 from thaJeztah/19.03_backport_add_tc_dynamic_ingress_network [19.03 backport] Add TC to check dynamic subnet for ingress network Upstream-commit: 075a0201b96af7c023f22341a8876a50ecc1828b Component: engine

view details

GordonTheTurtle

commit sha 4d79118906ccd70c40d1ca59a73e796fecb818a9

Merge component 'engine' from git@github.com:docker/engine 19.03

view details

Andrew Hsu

commit sha 074ef5074a8807932b5ed6b14cce28dd1a156ab5

bump ver 19.03.5-rc1 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 4 months

push eventdocker/engine

Sebastiaan van Stijn

commit sha 0c38d56a6dae8c9c8379d29083b759005308ebc9

Revert "Revert "[19.03] bump swarmkit to f35d9100f2c6ac810cc8d7de6e8f93dcc7a42d29"" This reverts commit ef4366ee890abc587b291f7e41223a2c51e14153. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Arko Dasgupta

commit sha 12e7d99439917b44a173e5326798365870bbbc90

Add TC to check dyanmic subnet for ingress network Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com> (cherry picked from commit e2b5ac75a393f6942c37efdd888fc3bc761de244) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Andrew Hsu

commit sha 075a0201b96af7c023f22341a8876a50ecc1828b

Merge pull request #374 from thaJeztah/19.03_backport_add_tc_dynamic_ingress_network [19.03 backport] Add TC to check dynamic subnet for ingress network

view details

push time in 4 months

PR merged docker/engine

[19.03 backport] Add TC to check dynamic subnet for ingress network

based on top of ~https://github.com/docker/engine/pull/281 and~ https://github.com/docker/engine/pull/376

depends on:

  • [ ] https://github.com/moby/moby/pull/39966 Add TC to check dynamic subnet for ingress network
  • [x] https://github.com/docker/engine/pull/281 [19.03 backport] Integration: change signatures to fix golint warnings
  • [x] https://github.com/docker/engine/pull/376 [19.03 backport] Fix flaky TestServiceWithDefaultAddressPoolInit

closes https://github.com/docker/engine/pull/375 (which is an alternative for this one)

Revert https://github.com/docker/engine/pull/375

brings back https://github.com/docker/engine/pull/369

full diff: https://github.com/docker/swarmkit/compare/bbe341867eae1615faf8a702ec05bfe986e73e06...f35d9100f2c6ac810cc8d7de6e8f93dcc7a42d29

changes included:

  • docker/swarmkit#2891 [19.03 backport] Remove hardcoded IPAM config subnet value for ingress network
    • backport of docker/swarmkit#2890 Remove hardcoded IPAM config subnet value for ingress network
    • fixes ENGCORE-1028 Specifying --default-addr-pool for docker swarm init is not picked up by ingress network

Backport of https://github.com/moby/moby/pull/39966 for 19.03

To fix CI being red after merging https://github.com/docker/engine/pull/369 (effectively a backport of https://github.com/moby/moby/pull/39953)

Marked as "WIP", because upstream isn't merged yet

+9 -7

5 comments

3 changed files

thaJeztah

pr closed time in 4 months

pull request commentdocker/engine

[19.03 backport] Add TC to check dynamic subnet for ingress network

known flaky failure

--- FAIL: TestDockerSwarmSuite/TestSwarmClusterRotateUnlockKey (61.38s)
thaJeztah

comment created time in 4 months

PR closed docker/engine

[19.03] Bump Swarmkit to f35d9100f2c6ac810cc8d7de6e8f93dcc7a42d29
  1. Includes: https://github.com/docker/swarmkit/pull/2891

  2. Edited TestServiceWithDefaultAddressPoolInit to validate dynamic ingress network subnet

Signed-off-by: Arko Dasgupta arko.dasgupta@docker.com

+9 -7

5 comments

3 changed files

arkodg

pr closed time in 4 months

pull request commentdocker/engine

[19.03] Bump Swarmkit to f35d9100f2c6ac810cc8d7de6e8f93dcc7a42d29

This is a duplicate of #374

arkodg

comment created time in 4 months

push eventandrewhsu/docker-ce

Andrew Hsu

commit sha a38f8a8fefdfaef720c1ca8267c5a37d794ab2bd

bump ver 19.03.5-rc1 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 4 months

startedmitchellh/gon

started time in 4 months

issue openedmoby/moby

run integration tests with selinux enabled

Currently, we're running tests without selinux enabled. Would be good to make sure stuff still goes with selinux enabled.

created time in 4 months

PR opened docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-rc1

bump ver

+1 -1

0 comment

1 changed file

pr created time in 4 months

create barnchandrewhsu/docker-ce

branch : 1903rc1

created branch time in 4 months

issue commentdocker/for-linux

unregister_netdevice waiting for IO

Hmm...looks like this moby issue has similar message about unregister_netdevice: https://github.com/moby/moby/issues/5618

zakikhani

comment created time in 4 months

issue closeddocker/for-linux

Docker build doesn't print the overridden value with --build-arg

<!-- This issue tracker is for bug reports and feature requests. For questions, and getting help on using docker:

  • Docker documentation - https://docs.docker.com
  • Docker Forums - https://forums.docker.com
  • Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
  • Post a question on StackOverflow, using the Docker tag -->
  • [x] This is a bug report
  • [ ] This is a feature request
  • [ ] I searched existing issues before opening this one

<!-- DO NOT report security issues publicly! If you suspect you discovered a security issue, send your report privately to security@docker.com. -->

Expected behavior

I have a Dockerfile with the following lines:

ARG PARENT=asdf.dkr.ecr.us-west-2.amazonaws.com/base:latest
FROM ${PARENT}

Sometimes I want to build this with a different PARENT, for which I add the following command line option: --build-arg PARENT=tests_base:33053_88719

I expect Docker to print variables according to this override,

Actual behavior

but this is what actually happens:

12:31:31  ---> 95a664e8bec8
12:31:32 Successfully built 95a664e8bec8
12:31:32 Successfully tagged tests_base:33053_89232
12:31:32 Building docker image tests:33053_89232
12:31:41 Sending build context to Docker daemon  1.658GB
12:31:42 Step 1/5 : ARG PARENT=asdf.dkr.ecr.us-west-2.amazonaws.com/base:latest
12:31:42 Step 2/5 : FROM ${PARENT}
12:31:42  ---> 95a664e8bec8

As you can see, tests_base:33053_89232 was built as 95a664e8bec8 and a new build with --build-arg PARENT=tests_base:33053_88719 used it as PARENT, but it still prints what's in the Dockerfile, not the overridden value, which is misleading.

Steps to reproduce the behavior

<!-- Describe the exact steps to reproduce. If possible, provide a minimum reproduction example; take into account that others do not have access to your private images, source code, and environment.

REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED") --> Define a Dockerfile with something like this:

ARG PARENT=asdf.dkr.ecr.us-west-2.amazonaws.com/base:latest
FROM ${PARENT}

and do a build with --build-arg PARENT=tests_base:33053_88719 option.

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:29:11 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:27:45 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 95
  Running: 7
  Paused: 0
  Stopped: 88
 Images: 1007
 Server Version: 19.03.2
 Storage Driver: aufs
  Root Dir: /var/lib/docker/aufs
  Backing Filesystem: extfs
  Dirs: 1195
  Dirperm1 Supported: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 4.15.0-66-generic
 Operating System: Ubuntu 18.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 61.47GiB
 Name: ip-10-150-14-172
 ID: ZJFE:DJF7:DUGP:WOGK:A66E:IVQS:X6HB:CKP4:SBRG:VROU:ZIBO:GWXF
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
WARNING: the aufs storage-driver is deprecated, and will be removed in a future release.

Additional environment details (AWS, VirtualBox, physical, etc.) Running on AWS instances.

closed time in 4 months

bra-fsn

issue commentdocker/for-linux

Docker build doesn't print the overridden value with --build-arg

Try using the new docker build with buildkit enabled. The next generation docker build work is going to be powered by buildkit.

bra-fsn

comment created time in 4 months

delete branch andrewhsu/docker-ce

delete branch : 1903b2

delete time in 4 months

push eventdocker/docker-ce

Andrew Hsu

commit sha a9ad5f6959504343106fffa48798334acfaf5809

bump ver 19.03.5-beta2 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

Andrew Hsu

commit sha a8f2e052c39b0e4021119735f4d0a88b7bd3d77f

Merge pull request #635 from andrewhsu/1903b2 [19.03] bump ver 19.03.5-beta2

view details

push time in 4 months

PR merged docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-beta2

bump ver

+3 -1

1 comment

2 changed files

andrewhsu

pr closed time in 4 months

pull request commentdocker/docker-ce

[19.03] bump ver 19.03.5-beta2

Merging to get builds going.

andrewhsu

comment created time in 4 months

push eventandrewhsu/docker-ce

Sebastiaan van Stijn

commit sha 99e61e27b6ae2296df29106e80e24adbe58b1bde

Do not disable sig-proxy when using a TTY This partially reverts https://github.com/moby/moby/commit/e0b59ab52b87b8fc15dd5534c3231fdd74843f9f, and does not automatically disable proxying signals in TTY-mode Before this change: ------------------------------------ Start a container with a TTY in one shell: ``` docker run -it --init --name repro-28872 busybox sleep 30 ``` then, in another shell, kill the docker cli: ``` kill `pgrep -f repro-28872` ``` Notice that the CLI was killed, but the signal not forwarded to the container; the container continues running ``` docker container inspect --format '{{ .State.Status }}' repro-28872 running docker container rm -f repro-28872 ``` After this change: ------------------------------------ Start a container with a TTY in one shell: ``` docker run -it --init --name repro-28872 busybox sleep 30 ``` then, in another shell, kill the docker cli: ``` kill `pgrep -f repro-28872` ``` Verify that the signal was forwarded to the container, and the container exited ``` docker container inspect --format '{{ .State.Status }}' repro-28872 exited docker container rm -f repro-28872 ``` Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit ee295049231c84e59d00b7cf31eaefb86d936aad) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 137b3cc89ec16730c3f9923ec158ce13a51f286f Component: cli

view details

Sebastiaan van Stijn

commit sha 1109168ceee6414ed0e8938acda5c9026c406a48

Add test for --sig-proxy with a TTY Add a test to verify that killing the docker CLI forwards the signal to the container. Test-case for moby/moby 28872 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 7cf1a8d4c96d198e208af2d75d14ab32b8c26dfe) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 79f5dbcd55a7aad3daabaa6f646509025aacf386 Component: cli

view details

Kir Kolyshkin

commit sha 30a660eac287a4f1d7ec3ab085ef4fad57d87a5e

TestSigProxyWithTTY: fix exec.CombinedOutput should not be used here because: - it redirects cmd Stdout and Stderr and we want it to be the tty - it calls cmd.Run which we already did While at it - use pty.Start() as it is cleaner - make sure we don't leave a zombie running, by calling Wait() in defer - use test.Name() for containerName Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit bc4ed69a23e1840b0ebae2b28531dd323cdba28f) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 149f69ca0604a8cdfbdef7e2f323d5c7dd208880 Component: cli

view details

Tonis Tiigi

commit sha 44c64cdeb6e1fb0ca9383fae7afa8dca5d2d9b2b

vendor: update buildkit to ff93519ee Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Upstream-commit: 25162d4a4ee031d409c3bb6d8a26ba81c45eb3a0 Component: engine

view details

Andrew Hsu

commit sha 0dabf1e8964c741b6b110b42b2c0d349454fb886

Merge pull request #2177 from thaJeztah/19.03_backport_fix_sig_proxy [19.03 backport] Do not disable sig-proxy when using a TTY Upstream-commit: 99c5edceb48d64c1aa5d09b8c9c499d431d98bb9 Component: cli

view details

GordonTheTurtle

commit sha 345e14b7af76ddba903b171a9c7dc3ac4fbd2266

Merge component 'cli' from git@github.com:docker/cli 19.03

view details

Andrew Hsu

commit sha 04f81cc905f4ad53dc7f8c64f81d3e23b3185a85

Merge pull request #420 from tonistiigi/1903-buildkit-update [19.03] vendor: update buildkit to ff93519ee Upstream-commit: 5d5083a57a1c071a935bc6a1be6b1b1cc5cf1ede Component: engine

view details

GordonTheTurtle

commit sha c7fe6bb395172bf47236864c4fe3e4769bc5c306

Merge component 'engine' from git@github.com:docker/engine 19.03

view details

Andrew Hsu

commit sha a9ad5f6959504343106fffa48798334acfaf5809

bump ver 19.03.5-beta2 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 4 months

PR closed docker/docker-ce

Corrected mistake for the word in Readme.md

It appears that the singular demonstrative This is modifying the plural noun. Consider using a plural demonstrative or a singular noun instead.

Please do not send pull requests to this docker/docker-ce repository.

We do, however, take contributions gladly.

See https://github.com/docker/docker-ce/blob/master/CONTRIBUTING.md

Thanks!

+1 -1

4 comments

1 changed file

anandbhagwat

pr closed time in 4 months

pull request commentdocker/docker-ce

Corrected mistake for the word in Readme.md

The word hosts is used as a verb, not a noun, in the sentence.

anandbhagwat

comment created time in 4 months

PR closed docker/docker-ce

give more time to delete and ask user once dco/no

deleting the old config files from docker.io (18.09.7-0ubuntu1~18.04.4) with aptitude nukes all the docker files from an existing and running docker-ce installation

Thanks!

+2 -2

2 comments

1 changed file

sjo00

pr closed time in 4 months

pull request commentdocker/docker-ce

give more time to delete and ask user once

This docker/docker-ce repo is a composite of upstream repos. The upstream repo for this PR's patch is https://github.com/moby/moby. Open your PR there if you still want to propose this change.

sjo00

comment created time in 4 months

PR opened docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-beta2

bump ver

+3 -1

0 comment

2 changed files

pr created time in 4 months

create barnchandrewhsu/docker-ce

branch : 1903b2

created branch time in 4 months

push eventdocker/engine

Tonis Tiigi

commit sha 25162d4a4ee031d409c3bb6d8a26ba81c45eb3a0

vendor: update buildkit to ff93519ee Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

view details

Andrew Hsu

commit sha 5d5083a57a1c071a935bc6a1be6b1b1cc5cf1ede

Merge pull request #420 from tonistiigi/1903-buildkit-update [19.03] vendor: update buildkit to ff93519ee

view details

push time in 4 months

PR merged docker/engine

[19.03] vendor: update buildkit to ff93519ee impact/changelog

https://github.com/moby/buildkit/pull/1243

Signed-off-by: Tonis Tiigi tonistiigi@gmail.com

changelog line:

- Fix builder-next: permission errors on using build secrets or ssh forwarding with userns-remap.
- Fix builder-next: copying a symlink inside an already copied directory.
+10 -24

0 comment

4 changed files

tonistiigi

pr closed time in 4 months

push eventdocker/cli

Sebastiaan van Stijn

commit sha 137b3cc89ec16730c3f9923ec158ce13a51f286f

Do not disable sig-proxy when using a TTY This partially reverts https://github.com/moby/moby/commit/e0b59ab52b87b8fc15dd5534c3231fdd74843f9f, and does not automatically disable proxying signals in TTY-mode Before this change: ------------------------------------ Start a container with a TTY in one shell: ``` docker run -it --init --name repro-28872 busybox sleep 30 ``` then, in another shell, kill the docker cli: ``` kill `pgrep -f repro-28872` ``` Notice that the CLI was killed, but the signal not forwarded to the container; the container continues running ``` docker container inspect --format '{{ .State.Status }}' repro-28872 running docker container rm -f repro-28872 ``` After this change: ------------------------------------ Start a container with a TTY in one shell: ``` docker run -it --init --name repro-28872 busybox sleep 30 ``` then, in another shell, kill the docker cli: ``` kill `pgrep -f repro-28872` ``` Verify that the signal was forwarded to the container, and the container exited ``` docker container inspect --format '{{ .State.Status }}' repro-28872 exited docker container rm -f repro-28872 ``` Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit ee295049231c84e59d00b7cf31eaefb86d936aad) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Sebastiaan van Stijn

commit sha 79f5dbcd55a7aad3daabaa6f646509025aacf386

Add test for --sig-proxy with a TTY Add a test to verify that killing the docker CLI forwards the signal to the container. Test-case for moby/moby 28872 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 7cf1a8d4c96d198e208af2d75d14ab32b8c26dfe) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Kir Kolyshkin

commit sha 149f69ca0604a8cdfbdef7e2f323d5c7dd208880

TestSigProxyWithTTY: fix exec.CombinedOutput should not be used here because: - it redirects cmd Stdout and Stderr and we want it to be the tty - it calls cmd.Run which we already did While at it - use pty.Start() as it is cleaner - make sure we don't leave a zombie running, by calling Wait() in defer - use test.Name() for containerName Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit bc4ed69a23e1840b0ebae2b28531dd323cdba28f) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Andrew Hsu

commit sha 99c5edceb48d64c1aa5d09b8c9c499d431d98bb9

Merge pull request #2177 from thaJeztah/19.03_backport_fix_sig_proxy [19.03 backport] Do not disable sig-proxy when using a TTY

view details

push time in 4 months

PR merged docker/cli

[19.03 backport] Do not disable sig-proxy when using a TTY impact/changelog status/2-code-review

backport of:

  • https://github.com/docker/cli/pull/1841 Do not disable sig-proxy when using a TTY
  • https://github.com/docker/cli/pull/2016 TestSigProxyWithTTY: fix

This partially reverts https://github.com/moby/moby/commit/e0b59ab52b87b8fc15dd5534c3231fdd74843f9f (https://github.com/moby/moby/pull/2426), and does not automatically disable proxying signals in TTY-mode

fixes https://github.com/moby/moby/issues/28872 (docker client doesn't pass signals when a terminal is attached) fixes https://github.com/moby/moby/issues/3793 docker client not passing signals to dockerd

relates to:

  • https://github.com/moby/moby/issues/9098 Kill docker exec command will not terminate the spawned process
    • This patch does not fix the docker exec case; it looks like there's no API to kill an exec'd process, so there's no signal-proxy for this yet

Before this change:

Start a container with a TTY in one shell:

docker run -it --init --name repro-28872 busybox sleep 30

then, in another shell, kill the docker cli:

kill `pgrep -f repro-28872`

Notice that the CLI was killed, but the signal not forwarded to the container; the container continues running

docker container inspect --format '{{ .State.Status }}' repro-28872
running

docker container rm -f repro-28872

After this change:

Start a container with a TTY in one shell:

docker run -it --init --name repro-28872 busybox sleep 30

then, in another shell, kill the docker cli:

kill `pgrep -f repro-28872`

Verify that the signal was forwarded to the container, and the container exited

docker container inspect --format '{{ .State.Status }}' repro-28872
exited

docker container rm -f repro-28872

- Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: -->

- Fix docker client doesn't pass signals when a terminal is attached

- A picture of a cute animal (not mandatory but encouraged)

+844 -5

0 comment

31 changed files

thaJeztah

pr closed time in 4 months

pull request commentmoby/moby

Run buildkit integration tests

@SamWhited i added b43076e to always generate a bundle tgz for the buildkit step. see https://github.com/moby/moby/pull/40023/commits/b43076e6977cf64dc7465c4ca55325cb2e282870#diff-58231b16fdee45a03a4ee3cf94a9f2c3R113 for how it collects files to put into the tgz.

tiborvass

comment created time in 4 months

push eventtiborvass/docker

Andrew Hsu

commit sha b43076e6977cf64dc7465c4ca55325cb2e282870

Jenkinsfile: always create bundles tgz for buildkit step Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 4 months

issue openeddocker/docker.github.io

clarify docker-ee s390x linux packages only for 17.06

Docker EE install instructions mention installing docker-ee on s390x (aka z systems). It should clarify that it is only applicable for 17.06, e.g. https://github.com/docker/docker.github.io/blob/master/install/linux/docker-ee/rhel.md

Since according to the compatibility matrix, docker-ee only had supported packages on s390x architecture for the 17.06 version: https://success.docker.com/article/compatibility-matrix

created time in 4 months

push eventdocker/engine

Andrew Hsu

commit sha 031ef2dc8e0510280c9e55d07b8287e0a73c7fcc

Windows: disable flaky test TestStartReturnCorrectExitCode Signed-off-by: Andrew Hsu <andrewhsu@docker.com> (cherry picked from commit 1be272ef76ec7f37d680525e725c1a17a85a32cf) Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

Andrew Hsu

commit sha 35913e58c2089c2d19eb02b611fc289d1c56f113

Merge pull request #419 from andrewhsu/xit [19.03] Windows: disable flaky test TestStartReturnCorrectExitCode

view details

push time in 4 months

delete branch andrewhsu/moby

delete branch : xit

delete time in 4 months

PR merged docker/engine

Reviewers
[19.03] Windows: disable flaky test TestStartReturnCorrectExitCode

The 19.03 branch has failures on the tests run after PR merges:

--- FAIL: TestDockerSuite/TestStartReturnCorrectExitCode (9.39s)
    docker_cli_start_test.go:198: assertion failed: 125 (exitCode int) != 12 (int): out: time="2019-10-30T18:28:20Z" level=error msg="error waiting for container: EOF" 

This PR is a clean backport of PR https://github.com/moby/moby/pull/40117

+15 -0

0 comment

1 changed file

andrewhsu

pr closed time in 4 months

issue commentmoby/moby

Copying non-root owned files between stages fails when running with userns remapping

I just reproduced the original issue with docker-ce 19.03.4 using the legacy builder, but stuff works with docker-ce 19.03.4 enabled with buildkit builds.

bash$ DOCKER_BUILDKIT=1 docker build --progress=plain --no-cache -t asdf .
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 150B done
#2 DONE 0.0s

#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s

#3 [internal] load metadata for docker.io/library/busybox:latest
#3 DONE 0.3s

#4 [foo 1/2] FROM docker.io/library/busybox@sha256:1303dbf110c57f3edf68d9f5...
#4 CACHED

#5 [foo 2/2] RUN touch x && chown 1:1 x
#5 DONE 0.6s

#6 [stage-1 2/3] COPY --from=foo x /
#6 DONE 0.1s

#7 [stage-1 3/3] RUN cat /etc/passwd && ls -al /
#7 0.509 root:x:0:0:root:/root:/bin/sh
#7 0.509 daemon:x:1:1:daemon:/usr/sbin:/bin/false
#7 0.509 bin:x:2:2:bin:/bin:/bin/false
#7 0.509 sys:x:3:3:sys:/dev:/bin/false
#7 0.509 sync:x:4:100:sync:/bin:/bin/sync
#7 0.509 mail:x:8:8:mail:/var/spool/mail:/bin/false
#7 0.509 www-data:x:33:33:www-data:/var/www:/bin/false
#7 0.509 operator:x:37:37:Operator:/var:/bin/false
#7 0.509 nobody:x:65534:65534:nobody:/home:/bin/false
#7 0.510 total 44
#7 0.510 drwxr-xr-x    1 root     root          4096 Oct 31 23:02 .
#7 0.510 drwxr-xr-x    1 root     root          4096 Oct 31 23:02 ..
#7 0.510 drwxr-xr-x    2 root     root         12288 Oct 28 18:40 bin
#7 0.510 drwxr-xr-x    5 root     root           340 Oct 31 23:02 dev
#7 0.510 drwxr-xr-x    1 root     root          4096 Oct 31 23:02 etc
#7 0.510 drwxr-xr-x    2 nobody   nogroup       4096 Oct 28 18:40 home
#7 0.510 dr-xr-xr-x  138 nobody   nogroup          0 Oct 31 23:02 proc
#7 0.510 drwx------    2 root     root          4096 Oct 28 18:40 root
#7 0.510 dr-xr-xr-x   13 nobody   nogroup          0 Oct 31 23:02 sys
#7 0.510 drwxrwxrwt    2 root     root          4096 Oct 28 18:40 tmp
#7 0.510 drwxr-xr-x    3 root     root          4096 Oct 28 18:40 usr
#7 0.510 drwxr-xr-x    4 root     root          4096 Oct 28 18:40 var
#7 0.510 -rw-r--r--    1 daemon   daemon           0 Oct 31 23:02 x
#7 DONE 0.6s

#8 exporting to image
#8 exporting layers
#8 exporting layers 0.1s done
#8 writing image sha256:c2d55532c926d9d6e7cc15086d8d3ca7567bcc2a5821d73ae2bef5985ca06d9e done
#8 naming to docker.io/library/asdf done
#8 DONE 0.1s
bash$ docker info | grep userns
WARNING: No swap limit support
  userns

Perhaps this issue should be renamed to emphasize it is only an issue with legacy builder.

michael42

comment created time in 4 months

pull request commentmoby/moby

Fix COPY --from with userns and non zero uid/gid files

I'm able to reproduce the error with docker-ce 19.03.4 legacy builder, but the issue that this PR is trying to fix does not exist with docker-ce 19.03.4 enabled with buildkit builds. I'd recommend using docker build with buildkit builds to work around this issue since that is what the docker engine is migrating towards as the default in the future.

This PR should be closed.

segevfiner

comment created time in 4 months

pull request commentmoby/moby

Fix COPY --from with userns and non zero uid/gid files

I'll have a go at reproducing the original issue this PR is trying to fix. Not sure if it is still a thing that needs to be fixed after #38599 has been merged.

segevfiner

comment created time in 4 months

pull request commentmoby/moby

[builder-next] fix squashing base image layer

Looks like this PR needs more work to be taken out of draft mode. @Blyschak you still working on this or should it be closed?

Blyschak

comment created time in 4 months

issue openedmoby/moby

jenkins nodes for user namespace PR checks

tracking issue

created time in 4 months

pull request commentmoby/moby

Fix AppArmor profile docker-default /proc/sys rule

A lot has changed in the master branch to the PR checks. If this could get a rebase, would then re-run with relevant tests (even though this PR doesn't have a specific test for this change) would be good to get official green before review. cc @justincormack

philsphicas

comment created time in 4 months

pull request commentmoby/moby

archive: refactor race fixing logic to prevent potential deadlock

@tiborvass when you get a chance, rebase this to get the latest tests run on this change

tiborvass

comment created time in 4 months

pull request commentmoby/moby

Make binary output targets use own build cmd

I think @tonistiigi is interested in this one

cpuguy83

comment created time in 4 months

pull request commentmoby/moby

awslogs & archive: prevent 2 goroutine leaks in test functions

Only failure is on cleanup:

...
00:59:51.554  DONE 273 tests, 6 skipped in 2589.479s
00:59:51.554  ---> Making bundle: .integration-daemon-stop (in bundles/test-integration)
00:59:51.554  ++++ cat bundles/test-integration/TestDockerDaemonSuite/TestFailedPluginRemove/d4edc54f8e62d/docker.pid
00:59:51.554  +++ kill 5469
00:59:51.554  /go/src/github.com/docker/docker/hack/make/.integration-daemon-stop: line 10: wait: pid 5469 is not a child of this shell
00:59:51.554  warning: PID 5469 from bundles/test-integration/TestDockerDaemonSuite/TestFailedPluginRemove/d4edc54f8e62d/docker.pid had a nonzero exit code
00:59:51.554  ++++ cat bundles/test-integration/docker.pid
00:59:51.554  +++ kill 7289

Similar failure in older PR: https://github.com/moby/moby/pull/39271#issuecomment-511586087

But all tests are green.

lzhfromustc

comment created time in 4 months

pull request commentmoby/moby

Windows: Build and use gotestsum for running all tests

Talked with vikram about this PR today. Looks like the junit report of failures is enough to make sure the github status of the PR checks is red even though the unix return code of that step is 0. This seems acceptable to get this PR in but needs work later to get the unix return code of the step to accurately reflect test failures.

thaJeztah

comment created time in 4 months

PR opened docker/engine

Reviewers
[19.03] Windows: disable flaky test TestStartReturnCorrectExitCode

The 19.03 branch has failures on the tests run after PR merges:

--- FAIL: TestDockerSuite/TestStartReturnCorrectExitCode (9.39s)
    docker_cli_start_test.go:198: assertion failed: 125 (exitCode int) != 12 (int): out: time="2019-10-30T18:28:20Z" level=error msg="error waiting for container: EOF" 

This PR is a clean backport of PR https://github.com/moby/moby/pull/40117

+15 -0

0 comment

1 changed file

pr created time in 4 months

create barnchandrewhsu/moby

branch : xit

created branch time in 4 months

pull request commentmoby/moby

Windows: Build and use gotestsum for running all tests

Workaround for now: #40155

thaJeztah

comment created time in 4 months

pull request commentmoby/moby

Windows: Build and use gotestsum for running all tests

Looks like the failures listed in the junit report are also seen in other PRs to moby: https://github.com/moby/moby/pull/40154#issuecomment-548000180

  • TestDebugInfo
  • TestInfoInsecureRegistries
  • TestInfoRegistryMirrors
thaJeztah

comment created time in 4 months

pull request commentmoby/moby

Windows: Build and use gotestsum for running all tests

I'm starting to see the junit reports of the test results in jenkins UI now, which is a great step: https://ci.docker.com/public/blue/organizations/jenkins/moby/detail/PR-39998/38/tests

thaJeztah

comment created time in 4 months

push eventdocker/engine

Kir Kolyshkin

commit sha 92a8618ddc48e0c6fe464035d618d0996a1ff266

Bump golang 1.12.12 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

view details

Andrew Hsu

commit sha ddb60aa6d1ba1d9bfbb655fa1f3c3359f82979aa

Merge pull request #418 from kolyshkin/19.03-go1.12.12 [19.03] Bump golang 1.12.12

view details

push time in 4 months

PR merged docker/engine

[19.03] Bump golang 1.12.12
+4 -4

0 comment

4 changed files

kolyshkin

pr closed time in 4 months

push eventdocker/docker-ce

Andrew Hsu

commit sha 4dfdc66276f21c4c4fcfc85fdf652d191b75ca35

bump ver 19.03.5-beta1 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

Andrew Hsu

commit sha 4fe4dc73f679cf8ec6ed4ca50c84270406c298d0

Merge pull request #634 from andrewhsu/1903b1 [19.03] bump ver 19.03.5-beta1

view details

push time in 4 months

PR merged docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-beta1

bump ver and update changelog from what was merged: https://github.com/docker/engine/pulls?utf8=%E2%9C%93&q=is%3Aclosed+milestone%3A19.03.5+label%3Aimpact%2Fchangelog

+13 -1

1 comment

2 changed files

andrewhsu

pr closed time in 4 months

pull request commentdocker/docker-ce

[19.03] bump ver 19.03.5-beta1

merging to get the build going

andrewhsu

comment created time in 4 months

push eventandrewhsu/docker-ce

Tim Sampson

commit sha c4b8f0fdce0d883c10ba0fbd8ab0a87c17c0b281

add rudimentary fish completions for docker network Signed-off-by: Tim Sampson <tim@sampson.fi> (cherry picked from commit 2f7b364cb397526812f13c0d6c107919e9516ca3) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 6c66c799c7fe1c7f58d022a6e343aea54c504df6 Component: cli

view details

Morten Hekkvang

commit sha 83a3adfba289906bcad01a689ba284fd76aa058c

Make service completion faster Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit f55c5b6566e52d3ead55bc0d96528bc2a39daeea) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 667bd9a1b8fd9bb2066fbb575e6359d15892707e Component: cli

view details

Morten Hekkvang

commit sha a669026198bf22ecf34b1ba4ee9964a1d48619d9

Fix substitution of comma to space character, suggested by @albers Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit b85e1e2efefcc06c8de426d003fa2936f2286bb4) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: c70ce79adc2e13e48d45c58301a371623d4aaf12 Component: cli

view details

Morten Hekkvang

commit sha 431ea11fc3013ff4fc802f55e2f71edcf759bff2

Move filtering to __docker_complete_services, as suggested by @albers Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit 6ebcc211a7a955b93297db1f0ad96237c14691ae) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 9447d7431b8354083e25dc5768bcba23c5256bd8 Component: cli

view details

Morten Hekkvang

commit sha e3ed8c3900f85cac87f2c06a315dbb9d2631a07b

Fix erroneous space indentation of shell script Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit fc19fb6d95da6a4496ffd170412918da3529eb99) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 69f0132397ba95e3a00d3b66cea905302b6a6c9b Component: cli

view details

Trapier Marshall

commit sha eeaca109e75d92303a3185fc152d747b32a13c8f

Add bash completion for `builder build` Signed-off-by: Trapier Marshall <trapier.marshall@docker.com> (cherry picked from commit 86ae871e0a229d08e7d9746a35fa71f5305dd7d7) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 2fe281d17066fe5b1af336cfc3fa21844dab62c9 Component: cli

view details

Harald Albers

commit sha bc78bc021cf5568f2b1e9368c5216165621beead

Add bash completion for `builder build` options Signed-off-by: Harald Albers <github@albersweb.de> (cherry picked from commit cd9b39fc524c3b5f63b99b6795216d2180b0bfba) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 57332bcea37ebd00954ad0c3d3574abea9cd3529 Component: cli

view details

Forest Johnson

commit sha b75545f98d36efc0b33b6282a9a3dcb9d4c95a55

Explain -s flag on docker ps https://github.com/docker/docker.github.io/issues/1520#issuecomment-467971886 Signed-off-by: Forest Johnson <fjohnson@peoplenetonline.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit f7ab2987c39162cd47c2f1738d1590e7226b5537) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: c4e5fd7e53a5a3dc89734c391099aed8b8a0b795 Component: cli

view details

Daniel Cassidy

commit sha 848e74335ba81878ffa5236b302be12d9b758e56

builder.md: Correct copy/paste error Signed-off-by: Daniel Cassidy <mail@danielcassidy.me.uk> (cherry picked from commit e9ada56a888a042476f370d2de45b0633f7f85f6) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 66f8d279c1dc7f0c18b05c6dc8b39a79b5c18fdf Component: cli

view details

Odin Ugedal

commit sha e286381ed288abbf51ec8d1c8f344b9d6de763f8

Fix phrasing when referring to the freezer cgroup Signed-off-by: Odin Ugedal <odin@ugedal.com> (cherry picked from commit a0dd6e025d6d18527931a24b9e7d71132c47e601) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: a90e5598a4acb89e45730c418520dba5eee6e58c Component: cli

view details

Daniel Artine

commit sha dfd6965e6fa466ff0dd82ed599137905cad32817

Updating deprecated command example in search.md --stars example is deprecated. Changing to --filter=stars=5 Signed-off-by: danielartine <daniel.artine@ufrj.br> (cherry picked from commit bba0a4d5ac225a28eb0bd1b14a086f7197e8d762) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: df5c7130df9b81548ff5c27528c11e4696550cca Component: cli

view details

Adrian Plata

commit sha 1b850e1fb234342179ae5e1585aa16137b35392d

Minor formatting changes and a typo fix. Signed-off-by: Adrian Plata <adrian.plata@docker.com> (cherry picked from commit ba7ec36de2c5c83d689f5d2e1f3e0d209606d8c3) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: aa45ea366c18ae1265c5e3910d7f7b22b9e4c0dd Component: cli

view details

Brandon Mitchell

commit sha 3467817e1c4f5ab345fcb3ae0e25bbb2cdaff484

Adjusting glossary reference and clarrifying the start of a Dockerfile Signed-off-by: Brandon Mitchell <git@bmitch.net> (cherry picked from commit 937ce69b4251d355db64eb88715ced76ed04b157) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: c050ae7fb168a9dd5cb8a65a72cc7d2ec7993cda Component: cli

view details

Daniel Helfand

commit sha d10e0ad1826742c4dd4cc83f184222e88eeeb520

update Jenkins Build Status urls for README Signed-off-by: danielhelfand <helfand.4@gmail.com> (cherry picked from commit 46f3f9ac047bc5d4fe22183275b4e25d91870608) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 9597e681cb1273616b2657662227df57b469c711 Component: cli

view details

Andrew Hsu

commit sha 584423dc0fd347c0b1f128501d62531829976dd9

Merge pull request #2176 from thaJeztah/19.03_backport_completion [19.03 backport] completion script updates and fixes Upstream-commit: 5cef8fc8e5067f88e2563446506ca0cf794dab0a Component: cli

view details

Andrew Hsu

commit sha 76c903b14a882462edd93ccea8e39f2d85c67f67

Merge pull request #2178 from thaJeztah/19.03_backport_docs_updates [19.03 backport] docs updates Upstream-commit: ad6c6670340a726e3f3fd280b17266ba1145aa3b Component: cli

view details

GordonTheTurtle

commit sha e39e995156d68e6fddd9d4caa46d30bdf1ce075f

Merge component 'cli' from git@github.com:docker/cli 19.03

view details

Andrew Hsu

commit sha 4dfdc66276f21c4c4fcfc85fdf652d191b75ca35

bump ver 19.03.5-beta1 Signed-off-by: Andrew Hsu <andrewhsu@docker.com>

view details

push time in 4 months

push eventdocker/cli

Forest Johnson

commit sha c4e5fd7e53a5a3dc89734c391099aed8b8a0b795

Explain -s flag on docker ps https://github.com/docker/docker.github.io/issues/1520#issuecomment-467971886 Signed-off-by: Forest Johnson <fjohnson@peoplenetonline.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit f7ab2987c39162cd47c2f1738d1590e7226b5537) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Daniel Cassidy

commit sha 66f8d279c1dc7f0c18b05c6dc8b39a79b5c18fdf

builder.md: Correct copy/paste error Signed-off-by: Daniel Cassidy <mail@danielcassidy.me.uk> (cherry picked from commit e9ada56a888a042476f370d2de45b0633f7f85f6) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Odin Ugedal

commit sha a90e5598a4acb89e45730c418520dba5eee6e58c

Fix phrasing when referring to the freezer cgroup Signed-off-by: Odin Ugedal <odin@ugedal.com> (cherry picked from commit a0dd6e025d6d18527931a24b9e7d71132c47e601) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Daniel Artine

commit sha df5c7130df9b81548ff5c27528c11e4696550cca

Updating deprecated command example in search.md --stars example is deprecated. Changing to --filter=stars=5 Signed-off-by: danielartine <daniel.artine@ufrj.br> (cherry picked from commit bba0a4d5ac225a28eb0bd1b14a086f7197e8d762) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Adrian Plata

commit sha aa45ea366c18ae1265c5e3910d7f7b22b9e4c0dd

Minor formatting changes and a typo fix. Signed-off-by: Adrian Plata <adrian.plata@docker.com> (cherry picked from commit ba7ec36de2c5c83d689f5d2e1f3e0d209606d8c3) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Brandon Mitchell

commit sha c050ae7fb168a9dd5cb8a65a72cc7d2ec7993cda

Adjusting glossary reference and clarrifying the start of a Dockerfile Signed-off-by: Brandon Mitchell <git@bmitch.net> (cherry picked from commit 937ce69b4251d355db64eb88715ced76ed04b157) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Daniel Helfand

commit sha 9597e681cb1273616b2657662227df57b469c711

update Jenkins Build Status urls for README Signed-off-by: danielhelfand <helfand.4@gmail.com> (cherry picked from commit 46f3f9ac047bc5d4fe22183275b4e25d91870608) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Andrew Hsu

commit sha ad6c6670340a726e3f3fd280b17266ba1145aa3b

Merge pull request #2178 from thaJeztah/19.03_backport_docs_updates [19.03 backport] docs updates

view details

push time in 4 months

PR merged docker/cli

[19.03 backport] docs updates impact/documentation kind/docs status/3-docs-review

backports of:

  • https://github.com/docker/cli/pull/1697 Explain -s flag on docker ps
    • relates to https://github.com/docker/docker.github.io/issues/1520 https://github.com/docker/docker.github.io/issues/1520#issuecomment-467971886 Explain the SIZE column in "docker ps -s" and what "virtual" keyword means
    • relates to https://github.com/docker/docker.github.io/pull/8371 Explain -s flag on docker ps
  • https://github.com/docker/cli/pull/2014 builder.md: Correct copy/paste error
  • https://github.com/docker/cli/pull/2053 Fix phrasing when referring to the freezer cgroup
    • relates to https://github.com/moby/moby/pull/39759 Fix phrasing when referring to the freezer cgroup
  • https://github.com/docker/cli/pull/2072 Updating deprecated command example in search.md
  • https://github.com/docker/cli/pull/2128 Minor formatting changes and a typo fix
  • https://github.com/docker/cli/pull/2133 Adjusting glossary reference and clarrifying the start of a Dockerfile
  • https://github.com/docker/cli/pull/2156 Correct Jenkins Build Status URLs for README
    • closes https://github.com/docker/cli/issues/2155 Jenkins Build Status in README
+43 -24

2 comments

9 changed files

thaJeztah

pr closed time in 4 months

push eventdocker/cli

Tim Sampson

commit sha 6c66c799c7fe1c7f58d022a6e343aea54c504df6

add rudimentary fish completions for docker network Signed-off-by: Tim Sampson <tim@sampson.fi> (cherry picked from commit 2f7b364cb397526812f13c0d6c107919e9516ca3) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Morten Hekkvang

commit sha 667bd9a1b8fd9bb2066fbb575e6359d15892707e

Make service completion faster Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit f55c5b6566e52d3ead55bc0d96528bc2a39daeea) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Morten Hekkvang

commit sha c70ce79adc2e13e48d45c58301a371623d4aaf12

Fix substitution of comma to space character, suggested by @albers Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit b85e1e2efefcc06c8de426d003fa2936f2286bb4) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Morten Hekkvang

commit sha 9447d7431b8354083e25dc5768bcba23c5256bd8

Move filtering to __docker_complete_services, as suggested by @albers Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit 6ebcc211a7a955b93297db1f0ad96237c14691ae) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Morten Hekkvang

commit sha 69f0132397ba95e3a00d3b66cea905302b6a6c9b

Fix erroneous space indentation of shell script Signed-off-by: Morten Hekkvang <morten.hekkvang@sbab.se> (cherry picked from commit fc19fb6d95da6a4496ffd170412918da3529eb99) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Trapier Marshall

commit sha 2fe281d17066fe5b1af336cfc3fa21844dab62c9

Add bash completion for `builder build` Signed-off-by: Trapier Marshall <trapier.marshall@docker.com> (cherry picked from commit 86ae871e0a229d08e7d9746a35fa71f5305dd7d7) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Harald Albers

commit sha 57332bcea37ebd00954ad0c3d3574abea9cd3529

Add bash completion for `builder build` options Signed-off-by: Harald Albers <github@albersweb.de> (cherry picked from commit cd9b39fc524c3b5f63b99b6795216d2180b0bfba) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Andrew Hsu

commit sha 5cef8fc8e5067f88e2563446506ca0cf794dab0a

Merge pull request #2176 from thaJeztah/19.03_backport_completion [19.03 backport] completion script updates and fixes

view details

push time in 4 months

PR merged docker/cli

Reviewers
[19.03 backport] completion script updates and fixes area/completion status/2-code-review

backports of:

  • https://github.com/docker/cli/pull/2066 add rudimentary fish completions for docker network
  • https://github.com/docker/cli/pull/2078 Contrib: Make bash completion faster for services
  • https://github.com/docker/cli/pull/2116 Add bash completion for builder build
  • https://github.com/docker/cli/pull/2125 Add bash completion for builder build options
+33 -7

1 comment

2 changed files

thaJeztah

pr closed time in 4 months

PR opened docker/docker-ce

Reviewers
[19.03] bump ver 19.03.5-beta1

bump ver and update changelog from what was merged: https://github.com/docker/engine/pulls?utf8=%E2%9C%93&q=is%3Aclosed+milestone%3A19.03.5+label%3Aimpact%2Fchangelog

+13 -1

0 comment

2 changed files

pr created time in 4 months

create barnchandrewhsu/docker-ce

branch : 1903b1

created branch time in 4 months

issue commentdocker/for-linux

/proc/sys/net/ipv4/ip_forward set to 1 when install and start docker

Docker needs to setup ip forwarding to function when doing networking. Docs for some more info.

willzhang

comment created time in 4 months

issue closeddocker/for-linux

/proc/sys/net/ipv4/ip_forward set to 1 when install and start docker

why /proc/sys/net/ipv4/ip_forward set to 1 when install and start docker,any dos for this ?what it mean?

[root@iZj6cetbb1qeqfstcehc34Z ~]# cat /proc/sys/net/ipv4/ip_forward                                                            
0
[root@iZj6cetbb1qeqfstcehc34Z ~]# 
[root@iZj6cetbb1qeqfstcehc34Z ~]# systemctl start docker
[root@iZj6cetbb1qeqfstcehc34Z ~]# cat /proc/sys/net/ipv4/ip_forward
1

closed time in 4 months

willzhang
more