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
Tell us about your request
A button (or cli command) that will reload the environment - running a "docker compose up" under the hood?
And/Or add compose labels to the containers, so one can change the running container in an environment with docker compose itself.
Which service(s) is this request for?
docker dev environment
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
When I am working on an environment with few containers, I need to change compose configuration, or install new system package in app container, like adding a new lib or bumping database version, which require a restart or rebuild of container(s). I want to be able to not have to delete the whole environment each time I do that.
Are you currently working around the issue?
As of today, I run VScode directly on the folder of my project, and execute docker compose commands, which make this docker dev env feature useless.
Additional context
Being able to recreate the environment IMO is a critical feature. Too many time a developer will have to change either the dockerfile(s) or compose files, or a part of the code that require the container to restart. Having to delete the env and recreating it is a painful process and can take time if you have lot of thing to pre-built. Or I fail to see the point of docker dev envs (?).
The text was updated successfully, but these errors were encountered:
Tell us about your request
A button (or cli command) that will reload the environment - running a "docker compose up" under the hood?
And/Or add compose labels to the containers, so one can change the running container in an environment with docker compose itself.
Which service(s) is this request for?
docker dev environment
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
When I am working on an environment with few containers, I need to change compose configuration, or install new system package in app container, like adding a new lib or bumping database version, which require a restart or rebuild of container(s). I want to be able to not have to delete the whole environment each time I do that.
Are you currently working around the issue?
As of today, I run VScode directly on the folder of my project, and execute docker compose commands, which make this docker dev env feature useless.
Additional context
Being able to recreate the environment IMO is a critical feature. Too many time a developer will have to change either the dockerfile(s) or compose files, or a part of the code that require the container to restart. Having to delete the env and recreating it is a painful process and can take time if you have lot of thing to pre-built. Or I fail to see the point of docker dev envs (?).
The text was updated successfully, but these errors were encountered: