vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Dev Container Connection Unstable (WSL Ubuntu 22.04 Using Podman)

Open bramankp opened this issue 2 years ago • 7 comments

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.84.0-insider
  • OS Version: Windows 10, WSL Ubuntu 22.04

Steps to Reproduce:

  1. WSL Ubuntu 22.04
  2. Install Podman
  3. Configure VSCode ["dev.containers.dockerPath": "podman"]
  4. Open Dev Container on project.
  5. Witness VSCode ManagementConnection continually reconnecting.

If you install Docker WSL Ubuntu 22.04 and reconfigure to use "docker" it is stable.

If you reproduce this on WSL Ubuntu 20.04 (using Podman) it is stable.

There is a tangible benefit to using Podman for the container service and this works on 20.04. Why doesn't it work on 22.04?

bramankp avatar Oct 17 '23 15:10 bramankp

2023-10-17 15:18:00.200 [info] [127.0.0.1][84130da3][ExtensionHostConnection] New connection established.
2023-10-17 15:18:00.246 [info] [127.0.0.1][84130da3][ExtensionHostConnection] <222> Launched Extension Host Process.
2023-10-17 15:18:05.634 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:11.164 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:16.773 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:22.287 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:27.817 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:33.539 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:39.076 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:44.614 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:50.541 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.
2023-10-17 15:18:56.074 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected.

bramankp avatar Oct 17 '23 15:10 bramankp

What are the Podman versions you are using on Ubuntu 20.04 and 22.04? This sounds like it might be a Podman issue.

chrmarti avatar Dec 07 '23 10:12 chrmarti

3.4.2 on Ubuntu 20.04 3.4.4 on Ubuntu 22.04

I mean it could be a podman issue but the key here is figuring out if it is (or if it's reproducible) so we can communicate with that team and figure out the solution (if there is something they need to do to fix it).

bramankp avatar Dec 11 '23 14:12 bramankp

Please append the Dev Containers log from when this happens. (F1 > Dev Containers: Show Container Log)

chrmarti avatar Dec 12 '23 11:12 chrmarti

I have the same issue using Ubuntu and podman 4.3.1 or 4.9.2. "Fun" fact, it does work properly on a Debian with podman 4.3.1. The symptom is as in the log provided (here in trace mode):

[36883 ms] Start: Run in Host: podman inspect --type container f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063
[37233 ms] Stop (350 ms): Run in Host: podman inspect --type container f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063
[37234 ms] Stop (352 ms): Reconnection attempt 4
[37241 ms] Port forwarding connection from 51655 > 45769 > 45769 in the container.
[37276 ms] Start: Run in Host: podman exec -i -u vscode -e VSCODE_REMOTE_CONTAINERS_SESSION=31660bed-c332-4c89-8202-176f42b476881707827737037 f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063 /home/vscode/.vscode-server/bin/abd2f3db4bdb28f9e95536dfa84d8479f1eb312d/node -e 
[37815 ms] Port forwarding 51655 > 45769 > 45769 stderr: Connection established
[40853 ms] Port forwarding process for 51655 > 45769 > 45769 in the container:
[
  {
    "pid": 30060,
    "ppid": 29716,
    "bin": "C:\\Program Files\\Microsoft VS Code\\Code.exe",
    "name": "Code.exe",
    "cmd": "\"C:\\Program Files\\Microsoft VS Code\\Code.exe\" --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --user-data-dir=\"C:\\Users\\lellerba\\AppData\\Roaming\\Code\" --standard-schemes=vscode-webview,vscode-file --enable-sandbox --secure-schemes=vscode-webview,vscode-file --bypasscsp-schemes --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --streaming-schemes --mojo-platform-channel-handle=2056 --field-trial-handle=1712,i,3319547390338628545,16721176663865457760,262144 --disable-features=CalculateNativeWinOcclusion,SpareRendererForSitePerProcess,WinRetrieveSuggestionsOnlyOnDemand /prefetch:8"
  }
]
[42877 ms] Port forwarding 51655 > 45769 > 45769 stderr: Error: timed out waiting for file /home/developer/.local/share/containers/storage/overlay-containers/f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063/userdata/29a2047bdbc1faee30476ffe93c23f03e7079cdf5a2b715fae6ab56436dba34c/exit/f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063
[42880 ms] Stop (5604 ms): Run in Host: podman exec -i -u vscode -e VSCODE_REMOTE_CONTAINERS_SESSION=31660bed-c332-4c89-8202-176f42b476881707827737037 f877ea0f78e3f233fcb97440bbe13102cceeaeb884588fe3372546b136e9d063 /home/vscode/.vscode-server/bin/abd2f3db4bdb28f9e95536dfa84d8479f1eb312d/node -e 
[42881 ms] Port forwarding 51655 > 45769 > 45769 terminated with code 255 and signal null.
[42882 ms] Port forwarding 51655 > 45769 > 45769: Local close

Ellerbach avatar Feb 13 '24 12:02 Ellerbach

After more investigations, the issue is coming from the podman side. common is breaking. An update is necessary to 2.1.2. For example:

wget https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/amd64/conmon_2.1.2~0_amd64.deb -O /tmp/conmon_2.1.2.deb
sudo apt install /tmp/conmon_2.1.2.deb

Ellerbach avatar Feb 13 '24 14:02 Ellerbach

Hey @chrmarti, this issue might need further attention.

@bramankp, you can help us out by closing this issue if the problem no longer exists, or adding more information.

vscodenpa avatar Jun 13 '24 12:06 vscodenpa

Adding a note that Ubuntu 24.04 LTS seems to work fine. So I suggest everyone avoid that middle step-child of 22.04 if they run into this problem and can use the more recent version of LTS. :)

bramankp avatar Jun 13 '24 20:06 bramankp