container name "/portainer" is already in use

[SplendidCondiment]

Hi all!
Disclaimer: I tried searching but the words "container" and "portainer" and "already" and "in" and "use" were ignored by the search because they are too common - so I could not check whether this situation is already covered.

Issue: The installer script complains that the container name "/portainer" is already in use. But I am already running Portainer for 40+ services and I am NOT about to change that portainer setup, not even its name. Truly, this new Portainer should not have such a generic name!

May I suggest to use a "yams-" prefix for all the YAMS containers?! That would avoid any naming conflicts.

I will try to edit my local YAMS installer and relevant files to do this locally, because really it ought to be done. Wish me luck

[rogs]

Hey @SplendidCondiment!

That's a great suggestion, thanks! In the meantime, you can remove the portainer container in the YAMS docker-compose file, it's not crucial so it's okay to delete. Just make sure you don't run yams upgrade, since it's going to overwrite the docker-compose file and re-enable Portainer (either way, that command is not in use right now, it's more of a "hard reset" mode)

Cheers and thanks for the feedback!

Roger.