profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/StefanScherer/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Stefan Scherer StefanScherer @docker Erlangen, Germany https://stefanscherer.github.io Engineering manager @docker, Microsoft MVP, Retired Docker Captain

docker/docker.github.io 3253

Source repo for Docker's Documentation

docker/cli 2942

The Docker CLI

docker/getting-started 1163

Getting started with Docker

hypriot/flash 954

Command line script to flash SD card images of any kind

DieterReuter/image-builder-rpi64 158

Build SD card image for Raspberry Pi 3 64bit

hypriot/cluster-lab 158

Hypriot Cluster Lab

hypriot/blog 88

Repository for the Hypriot Blog

hypriot/arm-compose 77

Automated build for docker-compose on ARM

hypriot/device-init 72

Initialize a device on boot with user defined configuration

hypriot/golang-armbuilds 69

Pre-compiled GOLANG tarballs for ARM devices.

created tagStefanScherer/choco-packer

tag1.7.4

Chocolatey 'packer' package

created time in 11 hours

release StefanScherer/choco-packer

1.7.4

released time in 11 hours

delete branch StefanScherer/choco-packer

delete branch : update-174

delete time in 11 hours

push eventStefanScherer/choco-packer

Stefan Scherer

commit sha d193901a2baecacee35dd963ae4c16db6ea348c3

Update Packer 1.7.4

view details

Stefan Scherer

commit sha e944814f8577c1771ad6b489fa4950fde1570660

Merge pull request #65 from StefanScherer/update-174 Update Packer 1.7.4

view details

push time in 11 hours

created tagStefanScherer/choco-docker-compose

tag1.29.2

Chocolatey 'docker-compose' package

created time in 12 hours

release StefanScherer/choco-docker-compose

1.29.2

released time in 12 hours

push eventStefanScherer/choco-docker-compose

Rui Lopes

commit sha e571fca4e934ed8edd2c92b9f19fafcdff199e75

Update docker-compose 1.29.2

view details

Stefan Scherer

commit sha ddc3a13c97983d9bb72215b21b677f88ab2b17f8

Merge pull request #54 from rgl/update-1.29.2 Update docker-compose 1.29.2

view details

push time in 12 hours

PullRequestReviewEvent

PR opened StefanScherer/choco-packer

Update Packer 1.7.4
+6 -6

0 comment

3 changed files

pr created time in 12 hours

create barnchStefanScherer/choco-packer

branch : update-174

created branch time in 12 hours

PullRequestReviewEvent

issue closeddocker/for-win

Dockercli.exe doesn't recognise -h or --help flags

<!-- Click these checkboxes after submitting, or place an "x" in them. -->

  • [x] I have tried with the latest version of Docker Desktop
  • [x] I have tried disabling enabled experimental features
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID: N/A

Actual behavior

PS C:\Program Files\Docker\Docker> .\DockerCli.exe -h
Usage: DockerCli.exe [Command]
  -h, --help, -Help: Show the help information for this command
PS C:\Program Files\Docker\Docker> .\DockerCli.exe --help
Usage: DockerCli.exe [Command]
  -h, --help, -Help: Show the help information for this command
PS C:\Program Files\Docker\Docker> .\DockerCli.exe --Help
PS C:\Program Files\Docker\Docker>

Expected behavior

Some beautiful help screen or command line arguments should show.

Information

  • Windows Version: 10 21H1 (build 19043.1110)
  • Docker Desktop Version: Checked for updates, nothing found, so I guess latest at time of writing
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: Nope

Steps to reproduce the behavior

  1. Open CMD or Powershell.
  2. Navigate to Docker Desktop folder
  3. run Dockercli.exe -h/--help/--Help
  4. Don't get a list of command-line args

closed time in 2 days

pieterhouwen

issue commentdocker/for-win

Dockercli.exe doesn't recognise -h or --help flags

Hi Pieer,

Thanks for the feedback. I'm glad you got Docker Desktop working again. Yes, I'm going to close this issue as we're not going to invest more time into the DockerCli.

pieterhouwen

comment created time in 2 days

issue commentdocker/for-win

Dockercli.exe doesn't recognise -h or --help flags

Hi @pieterhouwen DockerCli is an internal tool that we never documented and will probably remove at some point in the future.

That being said if you explained a little what you’re looking to do, there might be other ways?

pieterhouwen

comment created time in 2 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha 8a50096cbf94ec3b2793ce5f20003979d6a65e92

mcr.microsoft.com/azure-cli Signed-off-by: Stefan Scherer <stefan.scherer@docker.com>

view details

push time in 3 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha b4e1092f90fbee023eef07cd7fc545b150e602a1

Upload windows 10

view details

push time in 3 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha f4474d9e90a5e2291198c6327eeb8f902b20f821

Build windows 10

view details

push time in 4 days

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

issue commentchocolatey/choco

choco install package failed in docker container

Hi William, Sure, I took the Dockerfile from the first comment and added the comment to enable PowerShell line continuation sign, this also enables easier backslash support.

# escape=`
ARG WIN_VER="ltsc2019"
FROM mcr.microsoft.com/windows/servercore:$WIN_VER
WORKDIR C:\temp
ADD https://chocolatey.org/install.ps1 C:\TEMP\choco-install.ps1
SHELL ["cmd", "/S", "/C"]
RUN powershell C:\TEMP\choco-install.ps1
RUN choco install 7zip.install -y
RUN choco install msys2 --params "/NoUpdate /InstallDir:C:\msys2" -y

I created a fresh Windows Server 2019 in Azure, installed Docker as described here, then created a test folder with the Dockerfile and opened a PowerShell terminal and ran

docker build -t msys2 .

This worked fine for me. I also pushed the image to stefanscherer/msys2.

williamtu

comment created time in 9 days

PullRequestReviewEvent

issue closeddocker/for-mac

Minimum width too large on MacOS

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Mac software, which we respond to on a best-effort basis.

Support requests in this repository (i.e., trouble installing or using the software) will be ignored, but personalized support is available to Docker Pro and Team customers at https://hub.docker.com/support/desktop/, and community support is available from the Docker community Slack (https://www.docker.com/docker-community).

Issues without sufficient detail to debug them will be closed. They generally need a clear title and description, steps to reproduce, and a diagnostics ID. See https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for how to generate a diagnostics ID either from inside the app or from the command line.


-->

<!-- Click these checkboxes after submitting, or place an "x" in them. -->

  • [x ] I have tried with the latest version of Docker Desktop
  • [x ] I have tried disabling enabled experimental features
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID:

Expected behavior

Entire desktop window is visible on-screen.

Actual behavior

Window width cannot be reduced enough to make the entire window visible

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles FTW. -->
  • macOS Version: 11.4
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.5.2

Steps to reproduce the behavior

  • Change display scaling from default to "looks like 1280x800".
  • Move dock from bottom of screen to the left side.
  • Maximize the Docker Desktop window.
  • Right side of window is not visible.

Screen Shot 2021-07-16 at 21 06 48

Screen Shot 2021-07-16 at 21 03 57

closed time in 9 days

tonytx05

issue commentdocker/for-mac

Minimum width too large on MacOS

Thanks @tonytx05 for the report and details how to reproduce. I'll close this ticket as it's a duplicate of #5847 where we track the issue and post further updates.

tonytx05

comment created time in 9 days

issue commentdocker/for-mac

Settings window doesn't fit on screen

@sheerun Thanks for the report. We're looking for a solution. We'll keep this ticket open and report back.

sheerun

comment created time in 9 days

push eventStefanScherer/docker

Matt Morrison

commit sha ff1d9a3ec52e559443c7d36561c903755e57fa7d

Update v1.41.yaml fix containers/create 404 response description Signed-off-by: Matt Morrison <3241034+Emdot@users.noreply.github.com>

view details

Sebastiaan van Stijn

commit sha d92739713c633c155c0f3d8065c8278b1d8a44e7

seccomp.Syscall: embed runtime-spec Syscall type This makes the type better reflect the difference with the "runtime" profile; our local type is used to generate a runtime-spec seccomp profile and extends the runtime-spec type with additional fields; adding a "Name" field for backward compatibility with older JSON representations, additional "Comment" metadata, and conditional rules ("Includes", "Excludes") used during generation to adjust the profile based on the container (capabilities) and host's (architecture, kernel) configuration. This change introduces one change in the type; the "runtime-spec" type uses a `[]LinuxSeccompArg` for the `Args` field, whereas the local type used pointers; `[]*LinuxSeccompArg`. In addition, the runtime-spec Syscall type brings a new `ErrnoRet` field, allowing the profile to specify the errno code returned for the syscall, which allows changing the default EPERM for specific syscalls. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Sebastiaan van Stijn

commit sha c7cd1b9436ac381747a5c52dddac5a66f97c61f8

profiles/seccomp.Syscall: use pointers and omitempty These fields are optional, and this makes the JSON representation slightly less verbose. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Akihiro Suda

commit sha 8610d8ce4cd28fe17c0867fbcb0714135ba9bbb8

rootless: fix "x509: certificate signed by unknown authority" on openSUSE Tumbleweed openSUSE Tumbleweed was facing "x509: certificate signed by unknown authority" error, as `/etc/ssl/ca-bundle.pem` is provided as a symlink to `../../var/lib/ca-certificates/ca-bundle.pem`, which was not supported by `rootlesskit --copy-up=/etc` . See rootless-containers/rootlesskit issues 225 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

view details

Sebastiaan van Stijn

commit sha af1e74555aec5858a59573df3a920d108cec30d4

vendor: moby/term, Azure/go-ansiterm for golang.org/x/sys/windows compatibility - winterm: GetStdFile(): Added compatibility with "golang.org/x/sys/windows" - winterm: fix GetStdFile() falltrough - update deprecation message to refer to the correct replacement - add go.mod - Fix int overflow - Convert int to string using rune() full diff: - https://github.com/moby/term/compare/bea5bbe245bf407372d477f1361d2ff042d2f556...3f7ff695adc6a35abc925370dd0a4dafb48ec64d - https://github.com/Azure/go-ansiterm/compare/d6e3b3328b783f23731bc4d058875b0371ff8109...d185dfc1b5a126116ea5a19e148e29d16b4574c9 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Steffen Butzer

commit sha 0c1a125644f4626b294cdd4b5862a728b1d974a7

libnetwork: processEndpointCreate: Fix deadlock between getSvcRecords and processEndpointCreate References https://github.com/moby/moby/pull/42545 Signed-off-by: Steffen Butzer <steffen.butzer@outlook.com>

view details

Stefan Scherer

commit sha 7a6cac2b23dfa1ac60bb7d8fddd53a9a33917a23

Run s390x tests on Ubuntu 20.04 Signed-off-by: Stefan Scherer <stefan.scherer@docker.com>

view details

Sebastiaan van Stijn

commit sha 2a562b15833fe87adf03405edec6bd7235945f7f

Merge pull request #42569 from steffengy/master-2 libnetwork: processEndpointCreate: Fix deadlock between getSvcRecords and processEndpointCreate

view details

Roman Volosatovs

commit sha b308097ec3d741e45ea6c3ebdf8c877c5d1a0594

daemon/images: refactor image listing - Rename image summary constructor - Rename `newImage` into `newImageSummary`, since the returned type is `*types.ImageSummary` - Rename variables for clarity - Rename `newImage` into `summary`, since the variable type is `*types.ImageSummary` - Rename `imagesMap` into `summaryMap`, since the value type contained is `*types.ImageSummary` - Only compute `DiffSize` when more than 1 reference to the layer exists, since it is not used otherwise - Move variable declarations closer to where they are used Signed-off-by: Roman Volosatovs <roman.volosatovs@docker.com> Co-authored-by: Sebastiaan van Stijn <github@gone.nl>

view details

Adam Williams

commit sha 9f0e268b00d782b3c1cfa99f4ebbd6a3306f0f60

Fix use of unsafe ptr #42444 Signed-off-by: Adam Williams <awilliams@mirantis.com>

view details

Adam Williams

commit sha a8d92be6e863196166168621c440fcb4dd03d52e

Use crypto/rand Signed-off-by: Adam Williams <awilliams@mirantis.com>

view details

Roman Volosatovs

commit sha af3e5568fcca17bacb7d27d1bbff0b68bb855b83

daemon/images: fix shared size computation for filtered requests Signed-off-by: Roman Volosatovs <roman.volosatovs@docker.com>

view details

Sebastiaan van Stijn

commit sha b2891cd7385622fd05476c5d1b4d37e73db00e0c

Merge pull request #42587 from awmirantis/fix-unsafe-ptr-42444 Fix use of unsafe ptr #42444

view details

Sebastiaan van Stijn

commit sha ababae665dc711648ecad8d6309be9d8ec98e957

Merge pull request #42550 from rvolosatovs/fix_image_shared_size Fix SharedSize computation in `ImageService.Image` for filtered requests

view details

Tianon Gravi

commit sha c6dd474a496ee4a0978dd929f4e718d7c2bb892f

Merge pull request #42579 from thaJeztah/update-s390x-ubuntu-2004 Run s390x tests on Ubuntu 20.04

view details

Brian Goff

commit sha 45b45ad65b6f4a76f2bd0f768ef6edb10ebcc0bc

Merge pull request #42508 from thaJeztah/bump_term_ansiterm vendor: moby/term, Azure/go-ansiterm for golang.org/x/sys/windows compatibility

view details

Sebastiaan van Stijn

commit sha 42d2048b9d7ce09bb47e1179ffc9399406368596

Dockerfile: update go-swagger to fix validation on Go1.16 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Akihiro Suda

commit sha 3f53b2ef7fab1e72a0368ab53c4ed993f0f5653f

Merge pull request #42592 from thaJeztah/update_swagger_fork

view details

Sebastiaan van Stijn

commit sha 477244cca51173426779c67024411d6e6a709bc9

API: update API version to v1.42 Docker 20.10 was released with API v1.41, so any change in the API should now target v1.42. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Sebastiaan van Stijn

commit sha 2b5427b85371633c94d6c3ed3ae769d67c79f500

Merge pull request #42047 from Emdot/Emdot-patch-1 Fix containers/create 404 response description

view details

push time in 13 days

push eventStefanScherer/docker-cli

Sebastiaan van Stijn

commit sha 678c2fde9831d9c59cfd89cb03445d369a297d19

UX: don't reverse progress-bars when rolling back Commit https://github.com/moby/moby//commit/330a0035334871d92207b583c1c36d52a244753f introduced "synchronous" service update and rollback, using progress bars to show current status for each task. As part of that change, progress bars were "reversed" when doing a rollback, to indicate that status was rolled back to a previous state. Reversing direction is somewhat confusing, as progress bars now return to their "initial" state to indicate it was "completed"; for an "automatic" rollback, this may be somewhat clear (progress bars "move to the right", then "roll back" if the update failed), but when doing a manual rollback, it feels counter-intuitive (rolling back is the _expected_ outcome). This patch removes the code to reverse the direction of progress-bars, and makes progress-bars always move from left ("start") to right ("finished"). Before this patch ---------------------------------------- 1. create a service with automatic rollback on failure $ docker service create --update-failure-action=rollback --name foo --tty --replicas=5 nginx:alpine 9xi1w3mv5sqtyexsuh78qg0cb overall progress: 5 out of 5 tasks 1/5: running [==================================================>] 2/5: running [==================================================>] 3/5: running [==================================================>] 4/5: running [==================================================>] 5/5: running [==================================================>] verify: Waiting 2 seconds to verify that tasks are stable... 2. update the service, making it fail after 3 seconds $ docker service update --entrypoint="/bin/sh -c 'sleep 3; exit 1'" foo overall progress: rolling back update: 2 out of 5 tasks 1/5: running [==================================================>] 2/5: running [==================================================>] 3/5: starting [============================================> ] 4/5: running [==================================================>] 5/5: running [==================================================>] 3. Once the service starts failing, automatic rollback is started; progress-bars now move in the reverse direction; overall progress: rolling back update: 3 out of 5 tasks 1/5: ready [===========> ] 2/5: ready [===========> ] 3/5: running [> ] 4/5: running [> ] 5/5: running [> ] 4. When the rollback is completed, the progressbars are at the "start" to indicate they completed; overall progress: rolling back update: 5 out of 5 tasks 1/5: running [> ] 2/5: running [> ] 3/5: running [> ] 4/5: running [> ] 5/5: running [> ] rollback: update rolled back due to failure or early termination of task bndiu8a998agr8s6sjlg9tnrw verify: Service converged After this patch ---------------------------------------- Progress bars always go from left to right; also in a rollback situation; After updating to the "faulty" entrypoint, task are deployed: $ docker service update --entrypoint="/bin/sh -c 'sleep 3; exit 1'" foo foo overall progress: 1 out of 5 tasks 1/5: 2/5: running [==================================================>] 3/5: ready [======================================> ] 4/5: 5/5: Once tasks start failing, rollback is started, and presented the same as a regular update; progress bars go from left to right; overall progress: rolling back update: 3 out of 5 tasks 1/5: ready [======================================> ] 2/5: starting [============================================> ] 3/5: running [==================================================>] 4/5: running [==================================================>] 5/5: running [==================================================>] rollback: update rolled back due to failure or early termination of task c11dxd7ud3d5pq8g45qkb4rjx Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

KGB33

commit sha 2a167065d2b79f48b5f6450154294ba2594efc25

Cleaned up formatting/typesetting. Changed backticks to bold/italics, removed angle brackets. Signed-off-by: Kelton Bassingthwaite <KeltonBassingthwaite@gmail.com>

view details

Kelton Bassingthwaite

commit sha 918168c40f8c8871a5717b305023ec59bb1318a0

Bolded SIGKILL & fixed backslash escaping. SIGKILL is a literal and bolded in other documentation, such as https://man7.org/linux/man-pages/man7/signal.7.html. Signed-off-by: Kelton Bassingthwaite <KeltonBassingthwaite@gmail.com>

view details

Kelton Bassingthwaite

commit sha 384b59b7358968b53d0920ef6ce85b52ee309c74

Updated docker attach example. The previous example was out of date. I changed the distro & pined the tag to help prevent the new example from becoming out of date too. Signed-off-by: Kelton Bassingthwaite <KeltonBassingthwaite@gmail.com>

view details

Mathieu Champlon

commit sha 7190255a68018af93ea29f2213c0b3874f554943

Deprecate Kubernetes stack support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>

view details

Sebastiaan van Stijn

commit sha cfeab9cf05817186d005660ad574a890ee5fd8ad

Merge pull request #3166 from mat007/stack-kubernetes-depreciation Deprecate Kubernetes stack support

view details

Sebastiaan van Stijn

commit sha 4a6fe51157bf0199a933f44d1da09685f48fd8dd

Merge pull request #2940 from thaJeztah/rollback_progress_bars UX: don't reverse progress-bars when rolling back

view details

Mathieu Champlon

commit sha c05f0f5957f34ca5a17709849fb5979e1f24c64d

Deprecate Kubernetes stack support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>

view details

Mathieu Champlon

commit sha a033cdf5157fab0b4fd029cc4030df024ca7afdb

Deprecate Kubernetes context support Signed-off-by: Mathieu Champlon <mathieu.champlon@docker.com>

view details

Sebastiaan van Stijn

commit sha f782d1355effbbc7b41617085469d8881c7dd080

Merge pull request #3167 from mat007/stack-kubernetes-depreciation Deprecate Kubernetes stack support

view details

Sebastiaan van Stijn

commit sha d7a311ba74e86986431f90f0b250ef27ef17e97f

Merge pull request #3163 from KGB33/923_cleanup_docker_container_attach_man Cleaned up formatting/typesetting.

view details

Sebastiaan van Stijn

commit sha d738e7c4897602e5fa0e2d38a599348529242354

docker info: skip API connection if possible The docker info output contains both "local" and "remote" (daemon-side) information. The API endpoint to collect daemon information (`/info`) is known to be "heavy", and (depending on what information is needed) not needed. This patch checks if the template (`--format`) used requires information from the daemon, and if not, omits making an API request. This will improve performance if (for example), the current "context" is requested from `docker info` or if only plugin information is requested. Before: time docker info --format '{{range .ClientInfo.Plugins}}Plugin: {{.Name}}, {{end}}' Plugin: buildx, Plugin: compose, Plugin: scan, ________________________________________________________ Executed in 301.91 millis fish external usr time 168.64 millis 82.00 micros 168.56 millis sys time 113.72 millis 811.00 micros 112.91 millis time docker info --format '{{json .ClientInfo.Plugins}}' time docker info --format '{{.ClientInfo.Context}}' default ________________________________________________________ Executed in 334.38 millis fish external usr time 177.23 millis 93.00 micros 177.13 millis sys time 124.90 millis 927.00 micros 123.97 millis docker context use remote-ssh-daemon time docker info --format '{{.ClientInfo.Context}}' remote-ssh-daemon ________________________________________________________ Executed in 1.22 secs fish external usr time 116.93 millis 110.00 micros 116.82 millis sys time 144.36 millis 887.00 micros 143.47 millis And daemon logs: Jul 06 12:42:12 remote-ssh-daemon dockerd[14377]: time="2021-07-06T12:42:12.139529947Z" level=debug msg="Calling HEAD /_ping" Jul 06 12:42:12 remote-ssh-daemon dockerd[14377]: time="2021-07-06T12:42:12.140772052Z" level=debug msg="Calling HEAD /_ping" Jul 06 12:42:12 remote-ssh-daemon dockerd[14377]: time="2021-07-06T12:42:12.163832016Z" level=debug msg="Calling GET /v1.41/info" After: time ./build/docker info --format '{{range .ClientInfo.Plugins}}Plugin: {{.Name}}, {{end}}' Plugin: buildx, Plugin: compose, Plugin: scan, ________________________________________________________ Executed in 139.84 millis fish external usr time 76.53 millis 62.00 micros 76.46 millis sys time 69.25 millis 723.00 micros 68.53 millis time ./build/docker info --format '{{.ClientInfo.Context}}' default ________________________________________________________ Executed in 136.94 millis fish external usr time 74.61 millis 74.00 micros 74.54 millis sys time 65.77 millis 858.00 micros 64.91 millis docker context use remote-ssh-daemon time ./build/docker info --format '{{.ClientInfo.Context}}' remote-ssh-daemon ________________________________________________________ Executed in 1.02 secs fish external usr time 74.25 millis 76.00 micros 74.17 millis sys time 65.09 millis 643.00 micros 64.44 millis And daemon logs: Jul 06 12:42:55 remote-ssh-daemon dockerd[14377]: time="2021-07-06T12:42:55.313654687Z" level=debug msg="Calling HEAD /_ping" Jul 06 12:42:55 remote-ssh-daemon dockerd[14377]: time="2021-07-06T12:42:55.314811624Z" level=debug msg="Calling HEAD /_ping" Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Silvin Lubecki

commit sha 5f07d7d5a12423c0bc1fb507f4d006ad0cdfef42

Merge pull request #3179 from thaJeztah/optimize_info docker info: skip API connection if possible

view details

Brian Goff

commit sha 4ce521c5031ac0d912b34c33d67f8d810edc40d7

info: print errors to stderr Errors always need to go to stderr. This also fixes a test in moby/moby's integration-cli which is checking to see if errors connecting to the daemon are output on stderr. Signed-off-by: Brian Goff <cpuguy83@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Sebastiaan van Stijn

commit sha 9262fad23bf50cbc9c5ed2a1d50e057e4b0829da

Merge pull request #3044 from cpuguy83/fix_info_output info: print errors to stderr

view details

Sebastiaan van Stijn

commit sha 0ebdad7492b517724cd8ddf5b8c6a5cb05351f40

vendor: github.com/containerd/containerd v1.5.3 to reduce indirect dependencies full diff: https://github.com/containerd/containerd/compare/v1.5.2...v1.5.3 This removes the hcsshim dependency and other dependencies coming from that. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

view details

Silvin Lubecki

commit sha f84487ed5b18080ee0bbad8e9b4ab46536cf0dba

Merge pull request #3154 from thaJeztah/update_containerd_deps vendor: github.com/containerd/containerd v1.5.3 to reduce indirect dependencies

view details

push time in 13 days

IssuesEvent