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

Add bash start container command before vscode debug command #76457

Closed
rickstaa opened this issue Jul 2, 2019 · 4 comments
Closed

Add bash start container command before vscode debug command #76457

rickstaa opened this issue Jul 2, 2019 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions

Comments

@rickstaa
Copy link

rickstaa commented Jul 2, 2019

System information

  • OS: Ubuntu 16.04
  • VSCode: v1.36.0-insders
  • Singularity: 3.2.1

Problem description

I'm currently trying to debug a python script that needs access to a python environment that is inside a singularity container. I was, therefore, wondering if there is an option to set a pre to debug command before the debug command.

Example:

singularity run --nv CONTAINER; VSCODE debug command
@vscodebot
Copy link

vscodebot bot commented Jul 2, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@rickstaa rickstaa closed this as completed Jul 2, 2019
@vscodebot vscodebot bot added the extensions Issues concerning extensions label Jul 2, 2019
@rickstaa rickstaa changed the title external terminal options Add bash start container command before vscode debug command Jul 2, 2019
@rickstaa rickstaa reopened this Jul 2, 2019
@isidorn
Copy link
Contributor

isidorn commented Jul 2, 2019

VSCode does not support running debug from the command line. There is already an open feature request for that.
Thus closing this a duplicate of that issue (you can search for existing issues to find it)

@isidorn isidorn closed this as completed Jul 2, 2019
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 2, 2019
@rickstaa
Copy link
Author

rickstaa commented Jul 2, 2019

@isidorn Thanks for your answer. Can you maybe link it to the existing issue? I, unfortunately, could not find it using the debug from the command line search stream.

@isidorn
Copy link
Contributor

isidorn commented Jul 2, 2019

#10979

@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions
Projects
None yet
Development

No branches or pull requests

2 participants