Docker problems after restoring backup

Configuration
1

Hello All,

Not sure if the question should asked here but i’ll try it anyway.

After some stream problems i decided to restore my Home Assitant to a previous state by restoring a full backup. After restore i am trying to install phpMyadmin and another add on.
For now i’ll stick to phpmyadmin add-on.
I try to start the service but it stops with this error that the add on is already in use by antother container. this happens with more add ons i installed.

PHOTO-2022-09-09-20-46-34
PHOTO-2022-09-09-20-46-34466×512 35.2 KB

I started portainer to and saw that there are 15 containers!!?
conatinaers_main

If i go to the containers the list shows that there are only 8 containters.
environment
The listing of the container is showing that phpmyadmin is not running and also cant start within portainer.

containerlist

If i look at the images i see that there are unused images and images that were installed but are after the backup not there anymore. I deleted the add-ons after the full backup i restored.

Images

The log files are:

Logfile::
homeassistant.components.hassio
Source: components/hassio/websocket_api.py:123
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 00:59:30 (2 occurrences)
Last logged: 10:13:03

Failed to to call /addons/a0d7b954_phpmyadmin/stats - Container addon_a0d7b954_phpmyadmin is not running
Failed to to call /addons/47701997_voice-nl-rdh/restart - Can’t create container from addon_47701997_voice-nl-rdh: 409 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_47701997_voice-nl-rdh: Conflict (“Conflict. The container name “/addon_47701997_voice-nl-rdh” is already in use by container “18fb78a799e8e836fe462f3cc39cb8b450ac252dffbe1b0b1c74b0d8941e8ca9”. You have to remove (or rename) that container to be able to reuse that name.”)

pHpmyadmin logfile:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh

parse error: Expected string key before ‘:’ at line 1, column 4
[10:16:43] ERROR: Unknown HTTP error occured
Add-on:

Add-on version:
You are running the latest version of this add-on.
parse error: Expected string key before ‘:’ at line 1, column 4
[10:16:44] ERROR: Unknown HTTP error occured
System: ( / )
Home Assistant Core:
Home Assistant Supervisor:

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
parse error: Expected string key before ‘:’ at line 1, column 4
[10:16:45] ERROR: Unknown HTTP error occured
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/phpmyadmin.sh
parse error: Expected string key before ‘:’ at line 1, column 4
[10:16:46] ERROR: Unknown HTTP error occured
cont-init: info: /etc/cont-init.d/phpmyadmin.sh exited 139
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

My question is how can i resolve this problem/?

2

Looks Lille it’s trying to create an existing container “addon_47701997_voice-nl-rdh”

I would backup config folders and then backup system and move it off to different storage while you try to fix this. Next you can try deleting that container using portainer and see if that clears error. If error doesn’t clear you can reinstall and try restore again.

Ultimately if you have the config backed up you should be able to restore without issue.

3

Thank you for replying!
I am not sure if i understand you correctly.

There is a conflict with creating a container while starting phpmyadmin, and also for the voice-nl-rhd.
Lest focus on phpmyadmin.

in the main dashboard it says that there are 14 containers while in the list there are only 8. So there are 6 containers that are not visible in portainer.
If i look into the list of images then i can see that there are a few with the flag “Unused”.

Do you mean that i should remove one or more of the images that are unused?

Thanks in advance for the support.

4

This is supervised install so I am not completely familiar with how it manages containers

My presumption is it is trying to “create” an existing container instead of “restarting” it. This will not be allowed in docker. I’m also presuming php container relies on those that have not started and does not start

At the end of day I am suggesting trying to delete the container showing in log but not confident it will work. I further suggesting backing up everything before you try anything with the assumption that at the end of the day you’ll be bringing up an new install and restoring to that