Skip to content
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.

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

Unable to connect to remote container after upgrading beyond 1.63.1 #7174

Closed
NotoriousPyro opened this issue Sep 9, 2022 · 5 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers verified Verification succeeded

Comments

@NotoriousPyro
Copy link

Steps to Reproduce:
Unknown other than upgrading to 1.64.0 and beyond. I've not been able to upgrade Remote Containers or VS code due to this issue. I am stuck on 1.63.1 with remote containers 0.209.6.

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

This is possibly related somewhat to: #6685

I am using podman.

Container config:

{
  "workspaceMount": "/home/craig.crawford/mycodefolder",
  "workspaceFolder": "/home/craig.crawford/mycodefolder",
  "remoteUser": "${localEnv:USER}",
  "settings": {
    "terminal.integrated.shell.linux": "/usr/sbin/capsh",
    "terminal.integrated.shellArgs.linux": [
      "--caps=",
      "--",
      "-c",
      "exec \"$@\"",
      "/bin/sh",
      "${localEnv:SHELL}",
      "-l"
    ]
  },
  "remoteEnv": {
    "COLORTERM": "${localEnv:COLORTERM}",
    "DBUS_SESSION_BUS_ADDRESS": "${localEnv:DBUS_SESSION_BUS_ADDRESS}",
    "DESKTOP_SESSION": "${localEnv:DESKTOP_SESSION}",
    "DISPLAY": "${localEnv:DISPLAY}",
    "LANG": "${localEnv:LANG}",
    "SHELL": "${localEnv:SHELL}",
    "SSH_AUTH_SOCK": "${localEnv:SSH_AUTH_SOCK}",
    "TERM": "${localEnv:TERM}",
    "VTE_VERSION": "${localEnv:VTE_VERSION}",
    "XDG_CURRENT_DESKTOP": "${localEnv:XDG_CURRENT_DESKTOP}",
    "XDG_DATA_DIRS": "${localEnv:XDG_DATA_DIRS}",
    "XDG_MENU_PREFIX": "${localEnv:XDG_MENU_PREFIX}",
    "XDG_RUNTIME_DIR": "${localEnv:XDG_RUNTIME_DIR}",
    "XDG_SESSION_DESKTOP": "${localEnv:XDG_SESSION_DESKTOP}",
    "XDG_SESSION_TYPE": "${localEnv:XDG_SESSION_TYPE}"
  },
  "extensions": [
    "ms-python.python",
    "ms-python.vscode-pylance",
    "golang.go"
  ]
}

Yum packages and script used to create container is attached... though some of the commands the container runs will not be available due to them being makefile commands in a private repo: vscode.zip

Let me know if any more info is needed.

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Sep 9, 2022
@chrmarti
Copy link
Contributor

chrmarti commented Sep 12, 2022

ECONNREFUSED ::1:45393 suggests that it was using IPv6 to connect and the server only listens on 127.0.0.1. Changing that to explicitly use 127.0.0.1 on the connecting side to see if that's the problem. The change will be in the next Remote-Containers pre-release version.

@chrmarti chrmarti self-assigned this Sep 12, 2022
@chrmarti chrmarti added this to the September 2022 milestone Sep 12, 2022
@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Sep 12, 2022
@chrmarti chrmarti modified the milestones: September 2022, October 2022 Sep 30, 2022
@chrmarti
Copy link
Contributor

Fix is in Dev Containers (Remote-Containers) 0.253.0-pre-release. Could you check if that fixes it? Thanks!

@alexr00 alexr00 added the author-verification-requested Issues potentially verifiable by issue author label Sep 30, 2022
@vscodenpa
Copy link

This bug has been fixed in the latest pre-release!

@NotoriousPyro, you can help us out by commenting /verified if things are now working as expected.

Happy Coding!

@NotoriousPyro
Copy link
Author

/verified

@vscodenpa vscodenpa added verified Verification succeeded and removed author-verification-requested Issues potentially verifiable by issue author labels Sep 30, 2022
@NotoriousPyro
Copy link
Author

What's interesting to note is that it actually works in 0.251.0 as well 😕

@github-actions github-actions bot locked and limited conversation to collaborators Nov 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants