Deploying a stack after changing service names doesn't work good #22

New Issue

3wordchant · 2020-10-01T10:27:52Z

3wordchant commented

2020-10-01 10:27:52 +00:00

Steps to reproduce:

Define and deploy a stack, e.g. compose-stacks/wordpress
Edit the service names, e.g. rename wordpress → app and mariadb → db (see #19)
Re-deploy the service

The new app service never comes up because it can't connect to the database, the new db service can't start because of file locking clashes with the existing mariadb one.

docker stack rm demo_wordpress followed by a redeploy fixes it; this workaround may be all we need as I don't expect to have to rename services often. But, if there's a way to say "make sure other services called X are stopped first" then that'd be awesome.

Steps to reproduce: 1. Define and deploy a stack, e.g. [compose-stacks/wordpress](compose-stacks/wordpress) 2. Edit the service names, e.g. rename `wordpress` → `app` and `mariadb` → `db` (see #19) 3. Re-deploy the service The new `app` service never comes up because it can't connect to the database, the new `db` service can't start because of file locking clashes with the existing `mariadb` one. `docker stack rm demo_wordpress` followed by a redeploy fixes it; this workaround may be all we need as I don't expect to have to rename services often. But, if there's a way to say "make sure other services called X are stopped first" then that'd be awesome.

3wordchant added the

bug

label 2020-10-01 10:27:52 +00:00

3wordchant changed title from ~~Deploying a stack after changing services names doesn't work good~~ to Deploying a stack after changing service names doesn't work good

2020-10-01 10:27:59 +00:00

3wordchant referenced this issue from coop-cloud/wordpress

2020-10-01 10:34:27 +00:00

Rename services #11

decentral1se added

documentation

and removed

bug

labels 2020-10-27 07:59:18 +00:00

decentral1se added this to the Public mini-launch milestone 2020-10-27 08:05:04 +00:00

decentral1se added this to the (deleted) project 2020-12-27 11:49:14 +00:00

decentral1se removed this from the Public mini-launch milestone 2021-03-02 09:15:34 +00:00