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
I'm experiencing with the Gitlab container: https://github.com/CenturyLinkLabs/docker-gitlab on the "GitLab 7.3.0 with PostgreSQL and Redis". I was expecting that when I do panamax restart the state would be preserved, but everytime I do that, the Gitlab instance just keeps being reset and I have to do everything again...
Isn't there a way to pause panamax without losing the data? Pausing the VM in Virtual-Box and then restarting it completely breaks panamax (I need to perform a panamax restart after). How would this handle system restarts for example?
The text was updated successfully, but these errors were encountered:
Apparently new containers are always created on each restart instead of stopping and restarting the old ones... Is this the expected behaviour? How can I change this?
Local Panamax component versions:
UI: 0.2.20
API: 0.3.3
Still the same behaviour. This basically makes the technology useless for any serious/non-ephemeral use case imo, which is a pity considering the potential it has. I think kitematic now supports Linux, so I'm going to try that one instead. For anyone interested: https://github.com/kitematic/kitematic
I'll try to monitor the project in case you reach a more mature state though. Good luck!
I'm experiencing with the Gitlab container: https://github.com/CenturyLinkLabs/docker-gitlab on the "GitLab 7.3.0 with PostgreSQL and Redis". I was expecting that when I do panamax restart the state would be preserved, but everytime I do that, the Gitlab instance just keeps being reset and I have to do everything again...
Isn't there a way to pause panamax without losing the data? Pausing the VM in Virtual-Box and then restarting it completely breaks panamax (I need to perform a panamax restart after). How would this handle system restarts for example?
The text was updated successfully, but these errors were encountered: