10000 NPM CI gets blocked and docker container is not responding · Issue #7503 · docker/for-win · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

NPM CI gets blocked and docker container is not responding #7503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
cdudevops opened this issue Jun 30, 2020 · 3 comments
Closed
1 task done

NPM CI gets blocked and docker container is not responding #7503

cdudevops opened this issue Jun 30, 2020 · 3 comments
Labels
lifecycle/locked lifecycle/stale

Comments

@cdudevops
Copy link
cdudevops commented Jun 30, 2020 •
edited
Loading
  • I have tried with the latest version of my channel (Stable or Edge)

Expected behavior

I'm doing local development using docker on windows.
I created a docker compose where i bind a folder from my host inside docker container. When running npm ci from dockeer i'm expecting to work without issues.

Actual behavior

Running npm ci from docker is slowly deleting files till is getting blocked. In this point i'm forced to restart docker in order to run other commands from container

Information

Please, help us understand the problem. For instance:

  • Is it reproducible? yes

  • Is the problem new? nope

  • Windows Version: 10

  • Docker Desktop Version: latest

Steps to reproduce the behavior

  1. Install docker for windows
  2. docker-compose with bind volume from host containing node modules
@G-Rath
Copy link
G-Rath commented Sep 16, 2020

I'm having this problem too - It didn't occur in the previous major version, so I think this is one of the bugs caused by the new permission management setup.

I've seen a number of bugs get fixed - this one seems to be the last one left that I'm hitting so would love to get it resolved, as I think the new version contains some great new features.

Docker version 2.3.0.5 (48029).
Engine: 19.03.12
Compose: 1.27.2

Running Windows 10 Pro 1009 (18363.1082), using WSLv1.

I can reproduce this in my private project, but so far not been able to on my smaller attempt-to-reproduce project - I suspect this might relate to the number of dependencies being installed/removed.

This is my Diagnose ID uploaded before reproducing this issue: 54AB4182-2EB4-4638-9A2B-26C8B8D9C64C/20200916124137

I find this happen as soon as I run npm ci, and it tries to remove node_modules - hitting Ctrl + C does nothing, and I eventually have to force kill the container. This actually doesn't work: the container continues to run, and all attempts to stop it fail.

Attempting to exec into it results in the following:

OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "process_linux.go:101: executing setns process caused \"exit status 1\"": unknown

It looks to me based on the log output that the container has done a sort of complete crash, meaning its now in a processless-start that means when it comes back up it doesn't actually run anything.

This is my Diagnose ID uploaded after reproducing this issue: 54AB4182-2EB4-4638-9A2B-26C8B8D9C64C/20200916124708

Let me know if I can do anything else to help with this - like I said, this seems to be the only bug left that I'm hitting :)

This was referenced Sep 16, 2020
Closed
Closed
@docker-robott
Copy link
Collaborator

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

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Feb 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/locked lifecycle/stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@G-Rath @cdudevops @docker-robott
0