You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My workspace defines various docker-compose.yml files - e.g. to start a database, or some other service which I need while coding. So when I open the workspace, I first have to start those containers.
Please consider a feature which auto-starts specific containers when the workspace is opened, and auto-stops/removes them when the workspace is closed.
That would greatly simplify development.
The compose files could be specified in a project/.vscode/.docker config file, e.g.:
(That would be better than specifying it in the project/.vscode/settings.json as that would be checked into source control, whereas the project/.vscode/.docker config file is a per-developer preference - e.g. some devs must start the database, whereas others may start redis or whatever.)
My workspace defines various
docker-compose.ymlfiles - e.g. to start a database, or some other service which I need while coding. So when I open the workspace, I first have to start those containers.Please consider a feature which auto-starts specific containers when the workspace is opened, and auto-stops/removes them when the workspace is closed.
That would greatly simplify development.
The compose files could be specified in a
project/.vscode/.dockerconfig file, e.g.:{ "autoUp": [ "src/foo/docker-compose.yml" "src/bar/docker-compose.yml" ], "autoDown": [ "src/foo/docker-compose.yml" ], "autoRemove": [ "src/bar/docker-compose.yml" ] }(That would be better than specifying it in the
project/.vscode/settings.jsonas that would be checked into source control, whereas theproject/.vscode/.dockerconfig file is a per-developer preference - e.g. some devs must start the database, whereas others may start redis or whatever.)