search

krateng / maloja

Self-hosted music scrobble database to create personal listening statistics and charts
https://maloja.krateng.ch
GNU General Public License v3.0
1.17k stars 67 forks source link

Bogus containers? #214

Open janaxhell opened 1 year ago

janaxhell commented 1 year ago

I've just noticed that after deploying Maloja on my docker server, a few unknown and not running containers appeared in Portainer, with references to Maloja:

| ecstatic_aryabhata | exited |   | - | krateng/maloja | 2023-06-02 18:14:35 | - | - | administrators
| focused_lamarr | exited |   | - | krateng/maloja | 2023-06-02 17:33:41 | - | - | administrators
| determined_dirac | exited |   | - | krateng/maloja | 2023-06-02 17:31:42 | - | - | administrators
| hungry_vaughan | exited |   | - | krateng/maloja | 2023-06-02 17:28:25 | - | - | administrators
| quizzical_ritchie | exited |   | - | krateng/maloja | 2023-06-02 17:26:52 | - | - | administrators

What are these?

FoxxMD commented 1 year ago

AFAIK this is entirely dependent on your deployment. The example compose file lists only one container. If you are pulling straight from dockerhub its not possible to create more than one container (at a time).

Did you have any trouble initially getting the container to deploy? If the container was recreated without removing the old one those would just be left over containers that can be purged. When you edit a container from portainer you get a popup asking if the old container should be removed, if you did not do that then these would also be left over from that.

You could also just check for yourself...docker logs quizzical_ritchie will display output from the container. Or this can be accessed from the container details in portainer.

janaxhell commented 1 year ago

Yes, I did have problems, I posted about them here, then solved. But I always updated the stack/compose, not the container. Anyway I was worried someone somehow managed to get into my server and mess it, by the weird look of those names. I have already purged them, so I cannot check anything. I'm still a rookie in selfhosting, but in a year I have tried at least a hundred different applications and something like this never ever happened before. New bit learnt, thanks.

FoxxMD commented 1 year ago

The container names are automatically generated by docker.