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

[docker-compose] "runServices" not working if "service" already running #9118

Closed
mustafalim opened this issue Oct 20, 2023 · 3 comments
Closed
Assignees
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality

Comments

@mustafalim
Copy link

mustafalim commented Oct 20, 2023

  • VSCode Version: 1.83.1
  • Remote Extension/Connection Type: Containers

Given the devcontainer.json like:

{
	"name": "project-1",
	"dockerComposeFile": [
		"${localEnv:HOME}/Projects/docker/docker-compose.yml"
	],
	"service": "golang",
	"runServices": [
		"postgres"
	]
}
{
	"name": "project-2",
	"dockerComposeFile": [
		"${localEnv:HOME}/Projects/docker/docker-compose.yml"
	],
	"service": "golang",
	"runServices": [
		"mongo"
	]
}

For example, the two projects above are attached to the same container "golang", but both of them have different service dependencies. When the first project already opened, the second project "runServices" not running (postgres running but mongo not running), and vice versa.

To try the behaviour, I also tried to manually run golang container first before open vscode. When the "service" container (golang) already running, all "runServices" is ignored and not run already.

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Oct 20, 2023
@chrmarti chrmarti added the feature-request Request for new features or functionality label Dec 13, 2024
@vs-code-engineering vs-code-engineering bot added this to the Backlog Candidates milestone Dec 13, 2024
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

Copy link

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2025
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 feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants