Issue with HA installation on docker

Installation
9

Then the container isn’t even starting.

10

Oh i see… I thought it was since i got the running statut on portainer:

Capture
Capture1612×388 35.6 KB

Any idea what could block? Do you think it could come from the rights on the directory?

Thanks

11

Could be rights, but HA runs as root so that shouldn’t be it.

Sadly Portainer makes debugging stuff hard. Hopefully somebody who deals with it will be able to help you - I personally dislike it and just use docker compose for everything.

12

Anyway thanks a lot for your help. Thanks to you, some of the points I had doubts about have been clarified.

13

I used to use it myself, but I could have sworn I saw a release note that advised changing it.

1 Like
14

You did - 2023.7.x

2 Likes
15

Update: My container is not really running, it keeps on restarting:

Capture
Capture1895×125 8.99 KB

16

thanks - I’m not going mad…

1 Like
17

I would delete container and fully and start over. I cannot remember if need to specifically use arm image but is your system arm?

18

restarting may be because of:

restart: always
19

Im sorry but i don’t know what is an arm image or if my system is arm. I’m trying to deploy on my Nas which is a WD MyCloudEx2Ultra.
Thanks

20

Yeah i already set the option on “restart: unless-stopped” but it keeps restarting.
Thanks

21

The answer is yes then

That has a Marvell ARMADA385

I belive that needs anArm image?

1 Like
22

Indeed, but docker is smart enough to pick the proper architecture.
Actually, using the arch-specific image name has been deprecated a couple releases ago by HA.

I’m using the same home-assistant/home-assistant:stable image both on x64 and arm.

4 Likes
23

Try to do a docker logs homeassistant between restarts.
You might be lucky enough to get meaningful logs, still.

2 Likes
24

Hello Koying,
Thanks for your help.

Couldn’t get any log so far. I’ll keep trying.

It started all with this tutorial i found on the internet:
https://community.home-assistant.io/t/installing-home-assistant-on-wd-mycloudex2ultra/530270

I don’t know if it can be any helpful? i followed every step but still…

If i can catch any log i’ll let you know.
Thank you all.

25

This almost always ends with disappointment :laughing:

EDIT
I have had the same issue you have when docker randomly decide not to download the image or use the image downloaded. I think I remove container and reboot host and try again.

really you should be able to get HA running with no ports and no volumes mounted. I would step back and simply work on getting the container running then work on the rest. in portainer just add the image to use, give it a name and deploy works for HA if all is OK.

1 Like
26

:rofl: I’m new to this. I’m at the very beginning of the road to disappointment. So exciting :smiling_face_with_tear:

27

Gee. So much room for failures…
I assume you know what you’re doing regarding /mnt/ha/config ?

1 Like
28

Hello,
Thanks for your help. I gave it a try but it didn’t work. In the meantime I’ve understood that the container was restarting because of error code 139 and from what I’ve understood it seems that this is due to the fact that my NAS doesn’t have enough RAM. I have 1GB, do you think this is the problem?
Thanks