profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ndeloof/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.
Nicolas De loof ndeloof Docker Rennes, France http://blog.loof.fr Stuff Engineer

docker/awesome-compose 11860

Awesome Docker Compose samples

docker/cli 2894

The Docker CLI

compose-spec/compose-spec 764

The Compose specification

docker-archive/ecs-plugin 423

See http://github.com/docker/compose-cli

compose-spec/compose-go 131

Reference library for the parsing and loading Compose files

ndeloof/apache-maven-book 120

Apache Maven (le livre)

compose-spec/compose-ref 64

Compose specification reference implementation

docker-archive/cloud-integration-beta 29

Docker CLI with ACI integration (beta)

ndeloof/authobot 17

a docker authorization plugin to prevent abuses

cfpio/auth 2

authentication service

issue commentdocker/for-win

"No access token in response" when login in with MFA in Docker Desktop (Windows)

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

yooakim

comment created time in 40 minutes

issue commentdocker/for-win

Disable Update Pop-Up

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

doubledgedboard

comment created time in 40 minutes

issue commentdocker/for-win

Docker

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

Rakhat-iostream

comment created time in 40 minutes

issue commentdocker/for-win

Docker wsl2 crashed

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

Ivanrenes

comment created time in 41 minutes

issue commentdocker/for-mac

macOS: Terminal application by Configuration over Convention

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

marcofeltmann

comment created time in 41 minutes

issue commentdocker/for-mac

Unable to start K8S

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

lujijiang

comment created time in 41 minutes

issue commentdocker/for-mac

com.docker.hyperkit 25% cpu usage is back again #3499

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

taf2

comment created time in 41 minutes

issue commentdocker/for-mac

UnixHTTPConnectionPool(host='localhost', port=None): Read timed out on 2.4.0.0

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked

sdbruder

comment created time in 41 minutes

issue commentdocker/compose

Flag to set custom docker executable

@ndeloof Can you please reopen the issue? As @imgx64 said, the docker-compose build function notably does not use the Docker api and instead calls the Docker binary directly.

imgx64

comment created time in an hour

issue openeddocker/for-win

FeatureRequest: easily manage docker data on windows

Information

  • Windows Version: windows 10 21h1
  • Docker Desktop Version: 3.4.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Detail

On Windows, C Drive is normally smaller , and Docker is putting every data in C drive ! and We can not easily change to other drive, I think that will make us harder in Dev/Production

created time in an hour

issue commentdocker/for-win

Docker Desktop failed launch

I also:

  1. uninstalled docker desktop
  2. deselected [hyper-v & windows subsystem for linux] from windows features.
  3. restart & then installed the latest version of docker desktop
  4. checked windows subsystem for Linux from windows features.
  5. restarted & tried to start the docker, still, the same issue appeared.
zimmerkm

comment created time in 2 hours

issue openeddocker/for-win

Docker Desktop failed launch

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Windows 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
  • [ ] I have tried disabling enabled experimental features
  • [x ] I have uploaded Diagnostics
  • Diagnostics ID: 5B0A0CAE-7160-4E5A-9EFE-EE586D61F30C/20210624233438

Actual behavior

When I attempt to launch: System.InvalidOperationException: Failed to set version to docker-desktop: exit code: -1 stdout: Unsupported console settings. In order to use this feature, the legacy console must be disabled.

stderr: at Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:line 146 at Docker.Engines.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:line 82 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__26.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:line 178 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92

Expected behavior

Information

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

  • Is it reproducible? Yes
  • Is the problem new? Yes - This is a fresh install and this has never worked
  • Did the problem appear with an update? No - fresh install
  • uninstalled docker desktop
  • deselected [hyper-v & windows subsystem for linux] from windows features.
  • restart & then installed the latest version of docker desktop
  • checked windows subsystem for Linux from windows features.
  • restarted & tried to start the docker, still, the same issue appeared. -->
  • Windows Version: Win10 Pro 10.0.19043 N/A Build 19043
  • Docker Desktop Version: 3.5.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...Launch app
  2. ...

created time in 2 hours

issue commentdependabot/dependabot-core

invalid byte sequence in US-ASCII (ArgumentError)

@jurre My scene cannot use docker.

But I found the solution。Added the following script

export RUBYOPT="-KU -E utf-8:utf-8"

in the gitlab-ci.yml file

It solves the problem perfectly!Thanks for your answer!

wengjq

comment created time in 2 hours

issue commentdocker/for-mac

Ping by hostname in compose does not work from 3.4.0

Postgres container did not start without env variables

boskiv

comment created time in 2 hours

issue closeddocker/for-mac

Ping by hostname in compose does not work from 3.4.0

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

Expected behavior

DNS works

Actual behavior

DNS does not work

Information

  • macOS Version: 11.4
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.5.0

Steps to reproduce the behavior

version: '3'
services:
    postgres:
        image: postgres
    python:
        image: python
        depends_on:
          - postgres
docker compose run python bash
ping postgres

Output

root@17caf6cfde91:/# ping postgres
ping: postgres: Name or service not known

PS. This stop works from Docker Desktop for Mac after upgrading to 3.4.0

closed time in 2 hours

boskiv

issue closeddocker/for-win

Docker context not updated in WSL2 when changed from windows

  • [x] I have tried with the latest version of Docker Desktop
  • [x] I have tried disabling enabled experimental features
  • [-] I have uploaded Diagnostics : nope because i spent 2 hours fixing the issue and I don't want to go through the whole cycle again to get a diagnostic ID
  • Diagnostics ID:

Steps to reproduce the behavior

Create a remote docker context (from windows CLI) : docker context create "host=ssh:/...". remote Set that context default docker context use remote Upload and run some docker image into this context Restart use default context : docker context use default (from windows CLI) remove remote context : docker context rm remote Restart windows open wsl command line (ubuntu in my case) run docker context ls

Actual behavior

  • command hangs forever

Expected behavior

  • command displays default context (local)

Information

  • Is it reproducible? yes (see above)
  • Is the problem new? (don't know, at least two weeks)
  • Did the problem appear with an update? (don't know)
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. See above
  • Windows Version: 20H2 version 19042.804
  • Docker Desktop Version: 3.1.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No : bare metal

additional info

  • it seems that file ~/.docker/config.json was not updated properly (still using remote context) (and docker-win didn't fallback to default context)
  • manually editing this file (replace "remote" by "default") fixed the issue

closed time in 2 hours

JeWaVe

issue closeddocker/for-win

An error occured Docker

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Windows 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 a clear title, description, and diagnostics ID cannot be debugged, and will be closed.


-->

<!-- 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
  • [x] I have uploaded Diagnostics
  • Diagnostics ID:982ABEF2-687B-4522-87D9-386342E3A1BD/20210225085655

Actual behavior

Expected behavior

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 with reproduction inside is best. -->
  • Windows Version:
  • Docker Desktop Version:
  • WSL2 or Hyper-V backend?
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM:

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. ...
  2. ...

closed time in 2 hours

fenilgholani

issue closeddocker/for-win

Cannot Pull Windows Docker Images from WSL 2

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Click these checkboxes after submitting. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: 403FDAA4-2BA3-4C7B-A222-488FE2BB9CFF/20201218041947

Expected behavior

From within an integrated WSL 2 instance, I can pull and run Windows Docker images.

Actual behavior

Error response from daemon: Get https://docker-registry.a-company.com/v2/: dial tcp: lookup docker-registry.a-company.com on 192.168.65.1:53: read udp 192.168.65.3:57019->192.168.65.1:53: i/o timeout

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 with reproduction inside is best. -->
  • Windows Version: Windows 10 Pro 20H2 / 19042.685
  • Docker Desktop Version: 3.0.0 (50684)
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No.

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. Try to pull Windows docker images from a WSL 2 instance.
  2. Observe failures.

What have you tried

  • [x] Setting Docker Desktop's DNS settings to 8.8.8.8
  • [x] Setting WSL 2 instance's resolv.conf to nameserver 8.8.8.8
  • [x] Adding docker registry IP directly to Windows hosts file.
  • [x] Adding docker registry IP directly to Linux hosts file.
  • [x] Multiple restarts
  • [x] Swapping between Windows and Linux mode
  • [x] Waiting for months, upgrading Docker Desktop

closed time in 2 hours

wtchappell

issue closeddocker/for-mac

Docker is not starting

For some kind of reason Docker on Mac does not start anymore. Upgraded to 3.1.0 and downgraded after to 2.5.01.

In Mac pro (Catalina 10.5.7) Console I see: cannot ask lifecycle-server to start docker: Get "http://unix/docker/start": context deadline exceeded

closed time in 2 hours

githubkolja

issue commentdocker/for-mac

Ping by hostname in compose does not work from 3.4.0

➜  tmp docker network inspect tmp_default
[
    {
        "Name": "tmp_default",
        "Id": "2a3e5a5ac457108870f0732a370cd03390309de360e29b371e19d813a3d33ed0",
        "Created": "2021-06-25T01:36:48.076561054Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.19.0.0/16",
                    "Gateway": "172.19.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {},
        "Labels": {
            "com.docker.compose.network": "default",
            "com.docker.compose.project": "tmp",
            "com.docker.compose.version": "2.0.0"
        }
    }
]
boskiv

comment created time in 2 hours

issue commentdocker/for-mac

Ping by hostname in compose does not work from 3.4.0

It works on version 3.3.3

boskiv

comment created time in 2 hours

issue openeddocker/for-mac

Ping by hostname in compose does not work from 3.4.0

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

Expected behavior

DNS works

Actual behavior

DNS does not work

Information

  • macOS Version: 11.4
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.5.0

Steps to reproduce the behavior

version: '3'
services:
    postgres:
        image: postgres
    python:
        image: python
        depends_on:
          - postgres
docker compose run python bash
ping postgres

Output

root@17caf6cfde91:/# ping postgres
ping: postgres: Name or service not known

PS. This stop works from docker desktop after upgrading to Mac 3.4.0

created time in 2 hours

issue commentdocker/build-push-action

How to change the Context to other dir?

Solved: adding

- name: Checkout
  uses: actions/checkout@v2

At the beginning of the Github actions file

Can you share your file ,I add the check out ,it is also did not work

HiColinn

comment created time in 2 hours

issue commentdocker/for-win

Failed to deploy distro docker-desktop

@stephen-turner - as above, using Ubuntu on WSL2 on v2

mtnrbq

comment created time in 2 hours

issue commentdocker/for-win

Failed to deploy distro docker-desktop

wsl -l -v NAME STATE VERSION

  • Ubuntu Running 2
mtnrbq

comment created time in 2 hours

pull request commentdocker/cli

Enable ssh forwarding when building a remote target

Would love to get this merged @alexcb! Please let me know if I can help resolve the conflicts.

alexcb

comment created time in 2 hours

issue commentdocker/for-win

Volume mounts stopped working

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale

brentarias

comment created time in 3 hours

issue commentdocker/buildx

Error load metadata for docker.io/library/alpine:3.12 with v3.0.1

Update: https://stackoverflow.com/questions/64382812/docker-has-the-same-error-regardless-of-what-i-try-to-build-windows-10 helped me get rid of the issue.

This works for me, I deactived buildkit following https://stackoverflow.com/a/64466563

I installed Docker desktop on Windows 10 Edu with Debian for WSL2. I wanted to build the app of the tutorial https://docs.docker.com/get-started/02_our_app/ with a terminal connected to my Debian. I got the error of this issue when I was on Debian, but not on Windows with the powershell.

I still don't know why it has worked.

I ran into the issue with Debian for WSL2. I switched to powershell /terminal and it works. No clue either but your comment saved me!

puneri78

comment created time in 3 hours

PR opened dependabot/dependabot-core

poetry: ignore path dependencies in UpdateChecker

This PR updates the python UpdateChecker to ignore dependencies specified as a poetry path dependency.

There are two points of concern:

  • When querying for the latest versions, available indexes were queried. This is a privacy concern: customers with monorepos will leak every submodule's name to PyPI. (In my test setup, my internal module that I named nested was compared to https://pypi.org/project/Nested/ 😨 ).
  • When invoking poetry to query for resolvable versions, dependabot injects a version string to dependencies.

The latter causes a manifest like:

[tool.poetry.dependencies]
python = "^3.9"
nested = { path = "nested" }

To be re-written by Dependabot and fed to poetry as:

[tool.poetry.dependencies]
python = "^3.9"
nested = { path = "nested", version = ">= 0.1.0, <= 1.0.1" }

Which results in:

rsion_resolver.rb:88:in `block (2 levels) in fetch_latest_resolvable_version_string'
/home/dependabot/dependabot-core/python/lib/dependabot/python/update_checker/poetry_version_resolver.rb:338:in `run_poetry_command': RuntimeError (Dependabot::SharedHelpers::HelperSubprocessFailed)

  The Poetry configuration is invalid:
    - [dependencies.nested] {'path': 'nested', 'version': '>= 0.1.0, <= 1.0.1'} is not valid under any of the given schemas
  

  at /usr/local/.pyenv/versions/3.9.5/lib/python3.9/site-packages/poetry/core/factory.py:43 in create_poetry
       39│             message = ""
       40│             for error in check_result["errors"]:
       41│                 message += "  - {}\\n".format(error)
       42│ 
    →  43│             raise RuntimeError("The Poetry configuration is invalid:\\n" + message)
       44│ 
       45│         # Load package
       46│         name = local_config["name"]
       47│         version = local_config["version"]

Splitting between the PoetryVersionResolver and UpdateChecker is an unintentional byproduct of implementation order - I'd intended to only change the PoetryVersionResolver, but I didn't like seeing the PyPI results in the dry-run script output.

+48 -7

0 comment

5 changed files

pr created time in 3 hours

push eventdependabot/dependabot-core

Peter Wagner

commit sha df16f3be0ef3d11da30355aeaf3586ca828be957

poetry: ignore path dependencies in UpdateChecker

view details

push time in 3 hours