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
Sometimes containers are crashing, eg when I mount my source code into the local container and save some broken code. In this case I want to run gefyra restart $container-name to get it back up and running.
Why would such a feature be important to you?
Currently I can just stop and delete the container and execute gefyra run again, which is a loopway and additional work.
Anything else we need to know?
docker restart $container does partly work, but all the bridging will be broken. As soon as I want to connect to network services, it doesn't work anymore.
The text was updated successfully, but these errors were encountered:
This is a really good idea! I was briefly thinking about it - the main challenge here is probably to restore the bridge / run command / namespace ... parameters since these are not persisted anywhere.
In the past we had a look into labels - so an idea could be just to add labels to the container when it is actually created (it's only possible when the container is actually created).
Anyhow - this probably needs to investigation whether labels are a feasible solution to persist the containers flags.
What is the new feature about?
Sometimes containers are crashing, eg when I mount my source code into the local container and save some broken code. In this case I want to run
gefyra restart $container-name
to get it back up and running.Why would such a feature be important to you?
Currently I can just stop and delete the container and execute
gefyra run
again, which is a loopway and additional work.Anything else we need to know?
docker restart $container
does partly work, but all the bridging will be broken. As soon as I want to connect to network services, it doesn't work anymore.The text was updated successfully, but these errors were encountered: