Open depoortere opened 2 years ago
chrmarti
commented
2 years ago @depoortere Could you check if the latest version of the Remote-Containers extension (currently 0.231.4) fixes this? (We have made a few fixes related to 'Clone Repository'.)
depoortere
commented
2 years ago No same problem with 0.231.5, docker ps => 3f8d961c8411 vsc-volume-bootstrap "sleep infinity" About a minute ago Up About a minute agitated_cori
chrmarti
commented
2 years ago Could you check if the developer console has anything logged? (Help > Toggle Developer Tools)
Also please append the log from the latest version, maybe that has additional hints towards what is going on. Thanks.
depoortere
commented
2 years ago Test with 0.231.6
Starting Dev Container (show log) :
[103 ms] Remote-Containers 0.231.6 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977). [103 ms] Start: Resolving Remote [123 ms] Start: Check Docker is running [123 ms] Start: Run: docker version --format {{.Server.APIVersion}} [1738 ms] Server API version: 1.41 [1740 ms] Start: Run: docker volume ls -q [3647 ms] Start: Run: docker build -f C:\Users\D~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\D~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6 Sending build context to Docker daemon 729.6kB Step 1/4 : FROM mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14 ---> f42b89f7655a Step 2/4 : RUN apk add --no-cache nodejs npm make g++ docker-c li docker-compose ; ---> Using cache ---> e98667282deb Step 3/4 : RUN cd && npm i node-pty ---> Using cache ---> 0d25229b54ad Step 4/4 : COPY .vscode-remote-containers /root/.vscode-remote-containers ---> Using cache ---> 0481186d3706 Successfully built 0481186d3706 Successfully tagged vsc-volume-bootstrap:latest SECURITY WARNING: You are building a Docker image from Windows against a non-Win dows Docker host. All files and directories added to build context will have '-r wxr-xr-x' permissions. It is recommended to double check and reset permissions f or sensitive files and directories. Use 'docker scan' to run Snyk tests against images to find vulnerabilities and l earn how to fix them [8944 ms] Cloning Github repository: unknown-owner/testreact into /workspaces/testreact [8947 ms] Start: Run: docker run -d --mount type=volume,src=testreact-44d2e687fb9c09d9e45ad5486285d358,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock vsc-volume-bootstrap sleep infinity [11253 ms] Start: Run in container: /bin/sh [11678 ms] Start: Launching Remote-Containers helper. [11679 ms] ssh-agent: SSH_AUTH_SOCK in container (/tmp/vscode-ssh-auth-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.sock) forwarded to local host (\.\pipe\openssh-ssh-agent). [11680 ms] Start: Run: gpgconf --list-dir agent-extra-socket [11773 ms] findLocalWindowsExecutable: Exectuable 'gpgconf' not found on PATH 'C:\Program Files (x86)\Google\Chrome\Application;...'. [11778 ms] Start: Run in container: /bin/sh [12239 ms] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.js' >/tmp/vscode-remote-containers-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.js [13822 ms] [13822 ms] [13822 ms] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-server-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.js' >/tmp/vscode-remote-containers-server-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.js_1650360440037 [13829 ms] [13829 ms] [13833 ms] Start: Run in container: command -v git >/dev/null 2>&1 && git config --global --replace-all credential.helper '!f() { node /tmp/vscode-remote-containers-9ee6d368f6a0f3de01770f906b49c4cef1c5110e.js $*; }; f' || true [13837 ms] [13837 ms] [13839 ms] Start: Run in container: # Test for /root/.ssh/known_hosts and ssh [13842 ms] [13842 ms] [13843 ms] Start: Run in container: # Copy C:\Users\dxxx.ssh\known_hosts to /root/.ssh/known_hosts [13847 ms] [13847 ms]
Developer tools :
[Violation] Added non-passive event listener to a scroll-blocking
event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See [Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See log.ts:301 INFO Ignoring configured affinity for 'pub.name' because the extension is unknown or cannot execute. log.ts:301 INFO Invoking resolveAuthority(dev-container) abstractExtensionService.ts:114 The customer named _initialize has been holding on to the lock for 30s. This might be a problem. (anonymous) @ abstractExtensionService.ts:114
I use Rancher Desktop 1.2.1:
chrmarti
commented
2 years ago Unclear if related (also with Rancher Desktop): https://github.com/microsoft/vscode-remote-release/issues/6590
chrmarti
commented
2 years ago Does this work when cloning https://github.com/microsoft/vscode-remote-try-node ? (Reproduced #6590 with Rancher Desktop 1.2.1, but not this issue.)
depoortere
commented
2 years ago No !
[2022-05-01T16:33:13.850Z] Remote-Containers 0.231.6 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977). [2022-05-01T16:33:13.850Z] Start: Resolving Remote [2022-05-01T16:33:13.868Z] Start: Check Docker is running [2022-05-01T16:33:13.869Z] Start: Run: docker version --format {{.Server.APIVersion}} [2022-05-01T16:33:15.419Z] Stop (1550 ms): Run: docker version --format {{.Server.APIVersion}} [2022-05-01T16:33:15.420Z] Server API version: 1.41 [2022-05-01T16:33:15.420Z] Stop (1552 ms): Check Docker is running [2022-05-01T16:33:15.421Z] Start: Run: docker volume ls -q [2022-05-01T16:33:17.339Z] Stop (1918 ms): Run: docker volume ls -q [2022-05-01T16:33:17.339Z] Start: Run: docker volume create --label vsch.local.repository=https://github.com/microsoft/vscode-remote-try-node --label vsch.local.repository.unique=true vscode-remote-try-node-efc2391a72fae80452e138f39bd8bad2 [2022-05-01T16:33:19.288Z] Stop (1949 ms): Run: docker volume create --label vsch.local.repository=https://github.com/microsoft/vscode-remote-try-node --label vsch.local.repository.unique=true vscode-remote-try-node-efc2391a72fae80452e138f39bd8bad2 [2022-05-01T16:33:19.305Z] Start: Run: tar --no-same-owner -x -f - [2022-05-01T16:33:19.437Z] Stop (132 ms): Run: tar --no-same-owner -x -f - [2022-05-01T16:33:19.440Z] Start: Run: docker build -f C:\Users\DEPOOR~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\xxx~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6 [2022-05-01T16:33:20.157Z] [2022-05-01T16:33:23.996Z] Sending build context to Docker daemon 729.6kB Step 1/4 : FROM mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14 ---> f42b89f7655a Step 2/4 : RUN apk add --no-cache nodejs npm make g++ docker-cli docker-compose ; ---> Using cache ---> e98667282deb Step 3/4 : RUN cd && npm i node-pty ---> Using cache ---> 0d25229b54ad Step 4/4 : COPY .vscode-remote-containers /root/.vscode-remote-containers [2022-05-01T16:33:24.308Z] ---> c28b6afdb492 Successfully built c28b6afdb492 [2022-05-01T16:33:24.370Z] Successfully tagged vsc-volume-bootstrap:latest SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories. [2022-05-01T16:33:27.379Z] Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them [2022-05-01T16:33:27.439Z] Stop (7999 ms): Run: docker build -f C:\Users\xxx~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\xxx~1\AppData\Local\Temp\vsch\bootstrap-image\0.231.6 [2022-05-01T16:33:27.441Z] Cloning Github repository: microsoft/vscode-remote-try-node into /workspaces/vscode-remote-try-node [2022-05-01T16:33:27.442Z] Start: Run: docker run -d --mount type=volume,src=vscode-remote-try-node-efc2391a72fae80452e138f39bd8bad2,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock vsc-volume-bootstrap sleep infinity [2022-05-01T16:33:29.908Z] Stop (2466 ms): Run: docker run -d --mount type=volume,src=vscode-remote-try-node-efc2391a72fae80452e138f39bd8bad2,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock vsc-volume-bootstrap sleep infinity [2022-05-01T16:33:29.910Z] Start: Run in container: /bin/sh [2022-05-01T16:33:30.329Z] Start: Launching Remote-Containers helper. [2022-05-01T16:33:30.331Z] ssh-agent: SSH_AUTH_SOCK in container (/tmp/vscode-ssh-auth-be3f8326f4945be1a6a1765b6e6d2e571972d1de.sock) forwarded to local host (\.\pipe\openssh-ssh-agent). [2022-05-01T16:33:30.331Z] Start: Run: gpgconf --list-dir agent-extra-socket [2022-05-01T16:33:30.436Z] findLocalWindowsExecutable: Exectuable 'gpgconf' not found on PATH 'C:\Program Files (x86)\xxx'. [2022-05-01T16:33:30.440Z] Stop (109 ms): Run: gpgconf --list-dir agent-extra-socket [2022-05-01T16:33:30.440Z] Start: Run in container: /bin/sh [2022-05-01T16:33:30.441Z] Stop (112 ms): Launching Remote-Containers helper. [2022-05-01T16:33:30.442Z] Stop (111 ms): Run: gpgconf --list-dir agent-extra-socket [2022-05-01T16:33:30.900Z] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js' >/tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js [2022-05-01T16:33:32.376Z] [2022-05-01T16:33:32.376Z] [2022-05-01T16:33:32.376Z] Stop (1476 ms): Run in container: cat <<'EOF-/tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js' >/tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js [2022-05-01T16:33:32.377Z] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-server-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js' >/tmp/vscode-remote-containers-server-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js_1651422812377 [2022-05-01T16:33:32.385Z] [2022-05-01T16:33:32.385Z] [2022-05-01T16:33:32.385Z] Stop (8 ms): Run in container: cat <<'EOF-/tmp/vscode-remote-containers-server-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js' >/tmp/vscode-remote-containers-server-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js_1651422812377 [2022-05-01T16:33:32.388Z] Start: Run in container: command -v git >/dev/null 2>&1 && git config --global --replace-all credential.helper '!f() { node /tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js $; }; f' || true [2022-05-01T16:33:32.419Z] [2022-05-01T16:33:32.419Z] [2022-05-01T16:33:32.420Z] Stop (32 ms): Run in container: command -v git >/dev/null 2>&1 && git config --global --replace-all credential.helper '!f() { node /tmp/vscode-remote-containers-be3f8326f4945be1a6a1765b6e6d2e571972d1de.js $; }; f' || true [2022-05-01T16:33:32.423Z] Start: Run in container: # Test for /root/.ssh/known_hosts and ssh [2022-05-01T16:33:32.427Z] [2022-05-01T16:33:32.427Z] [2022-05-01T16:33:32.427Z] Stop (4 ms): Run in container: # Test for /root/.ssh/known_hosts and ssh [2022-05-01T16:33:32.427Z] Start: Run in container: # Copy C:\Users\xxx.ssh\known_hosts to /root/.ssh/known_hosts [2022-05-01T16:33:32.433Z] [2022-05-01T16:33:32.434Z] [2022-05-01T16:33:32.434Z] Stop (7 ms): Run in container: # Copy C:\Users\xxx.ssh\known_hosts to /root/.ssh/known_hosts [2022-05-01T16:33:32.764Z] Start: Run in container: git clone --depth 1 https://github.com/microsoft/vscode-remote-try-node . [2022-05-01T16:33:33.390Z] [2022-05-01T16:33:34.758Z] Cloning into '.'... [2022-05-01T16:33:35.350Z] remote: Enumerating objects: 15, done. remote: Counting objects: 100% (15/15), done. remote: Compressing objects: 100% (14/14), done. Receiving objects: 73% (11/15) [2022-05-01T16:33:35.380Z] remote: Total 15 (delta 0), reused 6 (delta 0), pack-reused 0 Receiving objects: 100% (15/15), 14.53 KiB | 826.00 KiB/s, done. [2022-05-01T16:33:35.504Z] Stop (2740 ms): Run in container: git clone --depth 1 https://github.com/microsoft/vscode-remote-try-node . [2022-05-01T16:33:35.511Z] Start: Run in container: cat /workspaces/vscode-remote-try-node/.devcontainer/devcontainer.json 2>/dev/null [2022-05-01T16:33:35.515Z] Stop (4 ms): Run in container: cat /workspaces/vscode-remote-try-node/.devcontainer/devcontainer.json 2>/dev/null [2022-05-01T16:33:35.519Z] Start: Run in container: cat /workspaces/vscode-remote-try-node/.devcontainer/devcontainer.json 2>/dev/null [2022-05-01T16:33:35.522Z] Stop (3 ms): Run in container: cat /workspaces/vscode-remote-try-node/.devcontainer/devcontainer.json 2>/dev/null [2022-05-01T16:33:35.505Z] Start: Run in container: git config remote.origin.fetch +refs/heads/:refs/remotes/origin/ [2022-05-01T16:33:36.487Z] [2022-05-01T16:33:37.669Z] Stop (2164 ms): Run in container: git config remote.origin.fetch +refs/heads/:refs/remotes/origin/ [2022-05-01T16:33:37.670Z] Start: Run in container: git fetch --unshallow --tags [2022-05-01T16:33:38.312Z] [2022-05-01T16:33:40.416Z] remote: Enumerating objects: 322, done. remote: Counting objects: 100% (322/322), done. remote: Compressing objects: 100% (156/156), done. [2022-05-01T16:33:40.447Z] Receiving objects: 52% (163/312) [2022-05-01T16:33:40.476Z] remote: Total 312 (delta 165), reused 301 (delta 154), pack-reused 0 Receiving objects: 100% (312/312), 67.13 KiB | 1.81 MiB/s, done. Resolving deltas: 100% (165/165), completed with 7 local objects. [2022-05-01T16:33:40.633Z] Stop (2963 ms): Run in container: git fetch --unshallow --tags
Developer Logs :
[Violation] Added non-passive event listener to a scroll-blocking
chrmarti
commented
2 years ago This last log looks like #6590. Please give Remote-Containers 0.233.1 pre-release a try and let me know if that fixes it.
depoortere
commented
2 years ago Yes, it's ok when I use https://github.com/microsoft/vscode-remote-try-node, the container started.
But it's not working with my own repo (gitlab on premise + vpn), block with container sleep infinity
[2022-05-04T16:28:20.966Z] Remote-Containers 0.233.1 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977). [2022-05-04T16:28:20.966Z] Start: Resolving Remote [2022-05-04T16:28:20.987Z] Start: Check Docker is running [2022-05-04T16:28:20.988Z] Start: Run: docker version --format {{.Server.APIVersion}} [2022-05-04T16:28:22.751Z] Stop (1763 ms): Run: docker version --format {{.Server.APIVersion}} [2022-05-04T16:28:22.752Z] Server API version: 1.41 [2022-05-04T16:28:22.752Z] Stop (1765 ms): Check Docker is running [2022-05-04T16:28:22.754Z] Start: Run: docker volume ls -q [2022-05-04T16:28:24.953Z] Stop (2199 ms): Run: docker volume ls -q [2022-05-04T16:28:24.955Z] Start: Run: docker build -f C:\Users\DEPOOR~1\AppData\Local\Temp\vsch\bootstrap-image\0.233.1\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\DEPOOR~1\AppData\Local\Temp\vsch\bootstrap-image\0.233.1 [2022-05-04T16:28:25.654Z] [2022-05-04T16:28:29.391Z] Sending build context to Docker daemon 736.8kB [2022-05-04T16:28:29.420Z] Step 1/4 : FROM mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14 ---> f42b89f7655a Step 2/4 : RUN apk add --no-cache nodejs npm make g++ docker-cli docker-compose ; ---> Using cache ---> e98667282deb Step 3/4 : RUN cd && npm i node-pty ---> Using cache ---> 0d25229b54ad Step 4/4 : COPY .vscode-remote-containers /root/.vscode-remote-containers ---> Using cache ---> 7eca274a038c Successfully built 7eca274a038c Successfully tagged vsc-volume-bootstrap:latest SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and r eset permissions for sensitive files and directories. [2022-05-04T16:28:30.257Z] Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them [2022-05-04T16:28:30.316Z] Stop (5361 ms): Run: docker build -f C:\Users\DEPOOR~1\AppData\Local\Temp\vsch\bootstrap-image\0.233.1\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\DEPOOR~1\AppData\Local\Temp\vsch\bootstrap-image\0.233.1 [2022-05-04T16:28:30.317Z] Cloning Github repository: unknown-owner/testreact into /workspaces/testreact [2022-05-04T16:28:30.318Z] Start: Run: docker run -d --mount type=volume,src=testreact-44d2e687fb9c09d9e45ad5486285d358,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock vsc-volume-bootstrap sleep infinity [2022-05-04T16:28:32.676Z] Stop (2358 ms): Run: docker run -d --mount type=volume,src=testreact-44d2e687fb9c09d9e45ad5486285d358,dst=/workspaces -v /var/run/docker.sock:/var/run/docker.sock vsc-volume-bootstrap sleep infinity [2022-05-04T16:28:32.677Z] Start: Run in container: /bin/sh [2022-05-04T16:28:33.107Z] Start: Launching Remote-Containers helper. [2022-05-04T16:28:33.107Z] ssh-agent: SSH_AUTH_SOCK in container (/tmp/vscode-ssh-auth-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.sock) forwarded to local host (\.\pipe\openssh-ssh-agent). [2022-05-04T16:28:33.108Z] Start: Run: gpgconf --list-dir agent-extra-socket [2022-05-04T16:28:33.207Z] findLocalWindowsExecutable: Exectuable 'gpgconf' not found on PATH 'C:\Program Files (x86)...'. [2022-05-04T16:28:33.213Z] Stop (105 ms): Run: gpgconf --list-dir agent-extra-socket [2022-05-04T16:28:33.214Z] Start: Run in container: /bin/sh [2022-05-04T16:28:33.216Z] Stop (109 ms): Launching Remote-Containers helper. [2022-05-04T16:28:33.216Z] Stop (108 ms): Run: gpgconf --list-dir agent-extra-socket [2022-05-04T16:28:33.711Z] Start: Run in container: echo ~ [2022-05-04T16:28:35.308Z] /root [2022-05-04T16:28:35.308Z] [2022-05-04T16:28:35.309Z] Stop (1598 ms): Run in container: echo ~ [2022-05-04T16:28:35.309Z] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js' >/tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js [2022-05-04T16:28:35.313Z] [2022-05-04T16:28:35.314Z] [2022-05-04T16:28:35.314Z] Stop (5 ms): Run in container: cat <<'EOF-/tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js' >/tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js [2022-05-04T16:28:35.314Z] Start: Run in container: cat <<'EOF-/tmp/vscode-remote-containers-server-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js' >/tmp/vscode-remote-containers-server-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js_1651681715314 [2022-05-04T16:28:35.320Z] [2022-05-04T16:28:35.320Z] [2022-05-04T16:28:35.321Z] Stop (7 ms): Run in container: cat <<'EOF-/tmp/vscode-remote-containers-server-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js' >/tmp/vscode-remote-containers-server-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js_1651681715314 [2022-05-04T16:28:35.325Z] Start: Run in container: command -v git >/dev/null 2>&1 && git config --global --replace-all credential.helper '!f() { node /tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js $; }; f' || true [2022-05-04T16:28:35.329Z] [2022-05-04T16:28:35.330Z] [2022-05-04T16:28:35.330Z] Stop (5 ms): Run in container: command -v git >/dev/null 2>&1 && git config --global --replace-all credential.helper '!f() { node /tmp/vscode-remote-containers-f53bc2cf38cc7e95e25095f25584b05ea9bb4d1f.js $; }; f' || true [2022-05-04T16:28:35.331Z] Start: Run in container: # Test for /root/.ssh/known_hosts and ssh [2022-05-04T16:28:35.334Z] [2022-05-04T16:28:35.335Z] [2022-05-04T16:28:35.335Z] Stop (4 ms): Run in container: # Test for /root/.ssh/known_hosts and ssh [2022-05-04T16:28:35.335Z] Start: Run in container: # Copy C:\Users\depoortere.ssh\known_hosts to /root/.ssh/known_hosts [2022-05-04T16:28:35.340Z] [2022-05-04T16:28:35.341Z] [2022-05-04T16:28:35.341Z] Stop (6 ms): Run in container: # Copy C:\Users\depoortere.ssh\known_hosts to /root/.ssh/known_hosts [2022-05-04T16:28:35.464Z] Start: Run in container: cat <<'EOF-/tmp/devcontainer-a32e99be-996f-4023-b445-56354186f82f.json' >/tmp/devcontainer-a32e99be-996f-4023-b445-56354186f82f.json_1651681715464 [2022-05-04T16:28:35.468Z] [2022-05-04T16:28:35.468Z] [2022-05-04T16:28:35.468Z] Stop (4 ms): Run in container: cat <<'EOF-/tmp/devcontainer-a32e99be-996f-4023-b445-56354186f82f.json' >/tmp/devcontainer-a32e99be-996f-4023-b445-56354186f82f.json_1651681715464 [2022-05-04T16:28:35.469Z] Start: Run in container: docker volume ls -q [2022-05-04T16:28:37.423Z] Stop (1954 ms): Run in container: docker volume ls -q [2022-05-04T16:28:41.092Z] Start: Run in container: tar --no-same-owner -x -f -
the devconsole : dom.ts:46 [Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952 l @ dom.ts:46 r @ dom.ts:67 registerTabsContainerListeners @ tabsTitleControl.ts:350 create @ tabsTitleControl.ts:180 F @ titleControl.ts:148 Jt @ tabsTitleControl.ts:149 _createInstance @ instantiationService.ts:110 createInstance @ instantiationService.ts:76 createTitleAreaControl @ editorGroupView.ts:489 Mi @ editorGroupView.ts:210 createInstance @ instantiationService.ts:110 createInstance @ instantiationService.ts:76 createNew @ editorGroupView.ts:65 doCreateGroupView @ editorPart.ts:544 doCreateGridControl @ editorPart.ts:999 createContentArea @ editorPart.ts:863 create @ part.ts:76 (anonymous) @ workbench.ts:351 renderWorkbench @ workbench.ts:348 (anonymous) @ workbench.ts:162 invokeFunction @ instantiationService.ts:61 startup @ workbench.ts:141 open @ desktop.main.ts:114 log.ts:301 INFO Ignoring configured affinity for 'pub.name' because the extension is unknown or cannot execute. log.ts:307 WARN [redhat.vscode-xml]: Cannot register 'redhat.telemetry.enabled'. This property is already registered. log.ts:307 WARN [redhat.vscode-yaml]: Cannot register 'redhat.telemetry.enabled'. This property is already registered. TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.yaml. Old grammar file: file:///c%3A/Users/depoortere/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json. New grammar file: file:///c%3A/Users/depoortere/.vscode/extensions/redhat.vscode-yaml-1.7.0/syntaxes/yaml.tmLanguage.json register @ TMScopeRegistry.ts:45 @ TMGrammarFactory.ts:73 _getOrCreateGrammarFactory @ abstractTextMateService.ts:227 await in _getOrCreateGrammarFactory (async) createTokenizationSupport @ abstractTextMateService.ts:251 _create @ tokenizationRegistry.ts:145 resolve @ tokenizationRegistry.ts:139 getOrCreate @ tokenizationRegistry.ts:71 (anonymous) @ abstractTextMateService.ts:152 _handle @ extensionsRegistry.ts:144 acceptUsers @ extensionsRegistry.ts:135 _handleExtensionPoint @ abstractExtensionService.ts:1243 _doHandleExtensionPoints @ abstractExtensionService.ts:1179 _startLocalExtensionHost @ extensionService.ts:569 await in _startLocalExtensionHost (async) _scanAndHandleExtensions @ extensionService.ts:531 _initialize @ abstractExtensionService.ts:747 await in _initialize (async) (anonymous) @ extensionService.ts:116 requestIdleCallback (async) e.runWhenIdle @ async.ts:1156 (anonymous) @ extensionService.ts:115 Promise.then (async) Fl @ extensionService.ts:113 _createInstance @ instantiationService.ts:110 _createServiceInstance @ instantiationService.ts:230 _createServiceInstanceWithOwner @ instantiationService.ts:219 _createAndCacheServiceInstance @ instantiationService.ts:208 _safeCreateAndCacheServiceInstance @ instantiationService.ts:151 _getOrCreateServiceInstance @ instantiationService.ts:135 _createInstance @ instantiationService.ts:88 createInstance @ instantiationService.ts:76 acquireInstantiationService @ configurationService.ts:461 (anonymous) @ workbench.ts:214 invokeFunction @ instantiationService.ts:61 initServices @ workbench.ts:208 startup @ workbench.ts:139 open @ desktop.main.ts:114 await in open (async) Y @ desktop.main.ts:380 m.load.configureDeveloperSettings @ workbench.js:32 (anonymous) @ bootstrap-window.js:181 i._invokeFactory @ loader.js:1185 i.complete @ loader.js:1195 i._onModuleComplete @ loader.js:1821 i._onModuleComplete @ loader.js:1833 i._resolve @ loader.js:1781 i.defineModule @ loader.js:1424 v @ loader.js:1871 define @ loader.js:1947 (anonymous) @ extensionService.ts:691 (anonymous) @ fake:1 log.ts:301 INFO Ignoring configured affinity for 'pub.name' because the extension is unknown or cannot execute.
chrmarti
commented
2 years ago This looks like a problem with how the docker executable sets up its stdio streams. Not sure if Rancher Desktop wraps that executable, but could you try the latest version of Rancher Desktop and if that doesn't fix it, try some older version with which it used to work?
depoortere
commented
2 years ago My previous answer was made with the latest Rancher Desktop 1.3.0. Note that the remote container v0.224.3 works perfectly with my usage.
Note that I'm using internal Docker images hosted on a Sonatype Nexus on premise. I don't use Microsoft's predefined images. Maybe there are settings of Dockers images that are not implemented for me.
chrmarti
commented
2 years ago I see this with Rancher Desktop when using a built-in configuration (e.g., with https://github.com/microsoft/vscode-azure-account).
Do you have a path with local configurations in your settings? With:
depoortere
commented
2 years ago Yes, I use this setting to have devcontainer.json to indicate the target image of my nexus, the https_proxy setting and the extensions to install.
An example on the repository that fails:
{
// Définit le nom du projet
"name": "TestReact",
// Image Docker à utiliser
"image": "mynexus/archiurba/vscode/centos7-nodejs16-angular12-git2:latest",
//
// Définir des arguments utilisés lors de l'exécution du container.
// Ici, pour activer le proxy lors de l'exécution du container.
"runArgs": [
"--name","testReact",
"-l","traefik.port=9090",
"-l","traefik.frontend.rule=Host:testReact.docker.localhost",
"-l","traefik.protocol=http",
"-l","traefik.docker.network=local_dev",
"--network","local_dev",
],
// Ajouter des variables au container (<=> Docker CLI : -e var=valeur )
"containerEnv": {
"HTTP_PROXY": "${localEnv:HTTP_PROXY}",
"HTTPS_PROXY": "${localEnv:HTTP_PROXY}",
"http_proxy": "${localEnv:HTTP_PROXY}",
"https_proxy": "${localEnv:HTTP_PROXY}",
"NO_PROXY": "localhost,127.0.0.0,127.0.1.1,local.home",
"TZ": "Europe/Paris",
"CHOKIDAR_USEPOLLING": "true",
},
//
// Définir les valeurs par défaut du settings.json dans le container.
"settings": {
"http.proxyStrictSSL": false,
"workbench.editor.labelFormat": "medium",
"workbench.colorCustomizations": {
"titleBar.activeBackground": "#09a2fa",
"titleBar.activeForeground": "#F6FBFB",
"titleBar.inactiveBackground": "#042664"
},
"emmet.includeLanguages": {
"javacript": "javascriptreact"
},
"emmet.triggerExpansionOnTab": true
},
//
// Ajouter les extensions suivantes au VSCode côté du container.
"extensions": [
"dsznajder.es7-react-js-snippets",
"mgmcdermott.vscode-language-babel",
"esbenp.prettier-vscode",
"formulahendry.auto-rename-tag",
"dbaeumer.vscode-eslint",
"Tyriar.sort-lines",
"bierner.emojisense",
"burkeholland.simple-react-snippets",
"xabikos.reactsnippets",
"fallenmax.mithril-emmet",
"eamodio.gitlens",
"mhutchie.git-graph"
],
//
// Exposer les ports du container au host en correspondance direct
"forwardPorts": [ 3000 ],
//
// Exécuter une commande après la création du container
"postCreateCommand": "git config --global http.sslVerify false && git config --global user.name \"Me\" && git config --global user.email \"me@mail\""
}
chrmarti
commented
2 years ago Upstream issue: https://github.com/rancher-sandbox/rancher-desktop/issues/2094
You could try using Rancher Desktop's WSL Integration:
I currently can't get Rancher Desktop's WLS integration working, so can't confirm if this would work. Let me know how it goes.
depoortere
commented
2 years ago If i set these parameters, nothing append : [2022-05-13T14:24:00.737Z] Start: Run: wsl -d UbuntuRancher -e wslpath -u C:\Users\depoortere\AppData\Local\Programs\Microsoft VS Code [2022-05-13T14:24:00.737Z] Remote-Containers 0.234.0 in VS Code 1.67.1 (da15b6fd3ef856477bf6f4fb29ba1b7af717770d). [2022-05-13T14:24:00.904Z] Stop (167 ms): Run: wsl -d UbuntuRancher -e wslpath -u C:\Users\depoortere\AppData\Local\Programs\Microsoft VS Code [2022-05-13T14:24:00.907Z] Start: Run: wsl -d UbuntuRancher -e /bin/sh -c cd '/mnt/c/Users/depoortere/AppData/Local/Programs/Microsoft VS Code' && /bin/sh [2022-05-13T14:24:00.941Z] Start: Run in host: id -un [2022-05-13T14:24:00.988Z] root [2022-05-13T14:24:00.989Z] [2022-05-13T14:24:00.989Z] Stop (48 ms): Run in host: id -un [2022-05-13T14:24:00.989Z] Start: Run in host: cat /etc/passwd [2022-05-13T14:24:00.991Z] Stop (2 ms): Run in host: cat /etc/passwd [2022-05-13T14:24:00.993Z] Start: Run in host: echo ~ [2022-05-13T14:24:00.994Z] /root [2022-05-13T14:24:00.995Z] [2022-05-13T14:24:00.995Z] Stop (2 ms): Run in host: echo ~ [2022-05-13T14:24:00.996Z] Start: Run in host: test -x '/root/.vscode-remote-containers/bin/da15b6fd3ef856477bf6f4fb29ba1b7af717770d/node' [2022-05-13T14:24:00.998Z] [2022-05-13T14:24:01.000Z] [2022-05-13T14:24:01.000Z] Stop (4 ms): Run in host: test -x '/root/.vscode-remote-containers/bin/da15b6fd3ef856477bf6f4fb29ba1b7af717770d/node' [2022-05-13T14:24:01.000Z] Start: Run in host: test -f '/root/.vscode-remote-containers/dist/vscode-remote-containers-server-0.234.0.js' [2022-05-13T14:24:01.002Z] [2022-05-13T14:24:01.002Z] [2022-05-13T14:24:01.003Z] Stop (3 ms): Run in host: test -f '/root/.vscode-remote-containers/dist/vscode-remote-containers-server-0.234.0.js' [2022-05-13T14:24:01.008Z] userEnvProbe: loginInteractiveShell (default) [2022-05-13T14:24:01.008Z] userEnvProbe shell: /bin/bash [2022-05-13T14:24:01.155Z] userEnvProbe PATHs: Probe: '/usr/local/sbin:/usr...' Container: None [2022-05-13T14:24:01.199Z] Start: Run in Host: docker version --format {{.Server.APIVersion}} [2022-05-13T14:24:01.252Z] Stop (53 ms): Run in Host: docker version --format {{.Server.APIVersion}} [2022-05-13T14:24:01.252Z] 1.41 [2022-05-13T14:24:07.043Z] Start: Run in Host: git ls-remote https://isi-forge.../depoortere/testreact.git
I'm trying different wsl image, start code from windows or from wsl command line, nothing append.
chrmarti
commented
2 years ago That might be the same issue. What do you get for which docker in WSL? Maybe that is using the Windows binaries. If so, you could try installing the Docker CLI in the WSL distro to avoid Rancher's binary.
depoortere
commented
2 years ago Which docker command return /usr/bin/docker in my wsl distrib associate with Rancher.
When rancher is down, docker images on the wsl failed with : Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
chrmarti
commented
2 years ago Could be an issue with the daemon then. The upstream issue https://github.com/rancher-sandbox/rancher-desktop/issues/2094 is now targeted for the "next" milestone. 🤞
Steps to Reproduce:
1.Ctrl+Shift+P > Remote Containers : Clone in container volume .. 2.Choose "Clone a repository from Gitlab (url on premise https) in a container volume 3.Choose project in list and choose https://mygitlab/myproject remote url 4.Execution stay on the last line of this log and in
docker psthe container vsc-volume-bootstrap stay on "sleep infinity"v0.224.3 still running correctly !
Does this issue occur when you try this locally?: Yes Does this issue occur when you try this locally and all extensions are disabled?: N/A