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

ignoreSync for path settings element #10333

Open
Malix-Labs opened this issue Sep 28, 2024 · 1 comment
Open

ignoreSync for path settings element #10333

Malix-Labs opened this issue Sep 28, 2024 · 1 comment
Assignees
Labels
containers Issue in vscode-remote containers

Comments

@Malix-Labs
Copy link

Malix-Labs commented Sep 28, 2024

Problem

  • dev.containers.dockerPath
  • dev.containers.dockerComposePath
  • dev.containers.repositoryConfigurationPaths
  • remote.SSH.path

Are local paths,
Thus could be different for each user's machine

Solution

Add "ignoreSync" : true to

  • dev.containers.dockerPath
  • dev.containers.dockerComposePath
  • dev.containers.repositoryConfigurationPaths
  • remote.SSH.path

Related

@Malix-Labs Malix-Labs changed the title dev.containers.dockerPath should be ignoreSync dev.containers.dockerPath && dev.containers.dockerComposePath should be ignoreSync Sep 28, 2024
@Malix-Labs Malix-Labs changed the title dev.containers.dockerPath && dev.containers.dockerComposePath should be ignoreSync ignoreSync for path settings element Sep 28, 2024
@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Sep 28, 2024
@Malix-Labs
Copy link
Author

I couldn't find the difference between ignoreSync and the "machine" scope, so I asked for vscode's clarification (see microsoft/vscode-docs#7638)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants