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

When operating on a remote VS Code Server, Remote Containers still executes on my local machine #4051

Closed
dmarszk opened this issue Nov 20, 2020 · 2 comments
Labels
containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)

Comments

@dmarszk
Copy link

dmarszk commented Nov 20, 2020

Issue Type: Bug

Scenario:

  • VS Code Workspace is on a remote server (accessed through VS Code Server via SSH)
  • The remote server is running Docker host
  • I attempt to attach to the running container via Remote Containers
  • Remote containers executes on my local machine instead of the remote server (effectively not being able to access the remote host)

Extension version: 0.148.1
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.19042
Remote OS version: Linux x64 4.4.0-190-generic
Remote OS version: Linux x64 4.4.0-190-generic
Remote OS version: Linux x64 4.4.0-19041-Microsoft
Remote OS version: Linux x64 4.12.14-122.37-default

System Info
Item Value
CPUs AMD Ryzen 7 3700X 8-Core Processor (16 x 4050)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 47.91GB (28.28GB free)
Process Argv --crash-reporter-id 298f8469-0e9e-467c-b32d-ea1a885601dd
Screen Reader no
VM 0%
Item Value
Remote SSH:
OS Linux x64 4.4.0-190-generic
CPUs Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz (4 x 2999)
Memory (System) 31.40GB (0.25GB free)
VM 11%
Item Value
Remote SSH:
OS Linux x64 4.4.0-190-generic
CPUs Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz (4 x 2999)
Memory (System) 31.40GB (0.25GB free)
VM 11%
Item Value
Remote WSL: Ubuntu-20.04
OS Linux x64 4.4.0-19041-Microsoft
CPUs AMD Ryzen 7 3700X 8-Core Processor (16 x 4050)
Memory (System) 47.91GB (28.29GB free)
VM 0%
Item Value
Remote SSH:
OS Linux x64 4.12.14-122.37-default
CPUs Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (8 x 2494)
Memory (System) 78.42GB (22.90GB free)
VM 67%
@github-actions github-actions bot added the containers Issue in vscode-remote containers label Nov 20, 2020
@ItalyPaleAle
Copy link

One other issue connected to this: when connected to a SSH remote, or when docker.host is non-local, clicking on "Open Folder in Container" should show a file picker on the remote host and not on the local machine.

@chrmarti
Copy link
Contributor

Addressing the 'attach' case in #4072. The more general support for Remote-SSH is tracked with #2994.

@chrmarti chrmarti added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 25, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jan 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants