When Enrico merges his dev-hub branch (https://github.com/esimonetti/SugarDockerized/tree/dev-hub) with Master, the container names for the Sugar Docker stack will change. We need to update the scripts, so we can avoid errors like the following:
ERROR: for sugar-permissions Cannot create container for service permissions: Conflict. The container name "/sugar-permissions" is already in use by container "5cbbe59bc188c841fc5504c8c71d04bccefa69893a7033935bd7ea3acc0c59cc". You have to remove (or rename) that container to be able to reuse that name.
We don't want to make the change until Enrico makes his update first.
Upon testing this out a bit more, it looks like the issue occurred when we switched between two different versions of Sugar. Two issues:
We were failing to stop the sugar-permissions container.
Old containers with the same name that were stopped but not removed were preventing new containers of the same name but from a different stack from being started.
When Enrico merges his dev-hub branch (https://github.com/esimonetti/SugarDockerized/tree/dev-hub) with Master, the container names for the Sugar Docker stack will change. We need to update the scripts, so we can avoid errors like the following:
ERROR: for sugar-permissions Cannot create container for service permissions: Conflict. The container name "/sugar-permissions" is already in use by container "5cbbe59bc188c841fc5504c8c71d04bccefa69893a7033935bd7ea3acc0c59cc". You have to remove (or rename) that container to be able to reuse that name.
We don't want to make the change until Enrico makes his update first.