#LOg

1 messages · Page 1 of 1 (latest)

tardy badger
#

2022-12-06 12:02:51 s6-rc: info: service s6rc-oneshot-runner: starting
2022-12-06 12:02:51 s6-rc: info: service s6rc-oneshot-runner successfully started
2022-12-06 12:02:51 s6-rc: info: service fix-attrs: starting
2022-12-06 12:02:51 s6-rc: info: service fix-attrs successfully started
2022-12-06 12:02:51 s6-rc: info: service legacy-cont-init: starting
2022-12-06 12:02:51 s6-rc: info: service legacy-cont-init successfully started
2022-12-06 12:02:51 s6-rc: info: service legacy-services: starting
2022-12-06 12:02:51 services-up: info: copying legacy longrun home-assistant (no readiness notification)
2022-12-06 12:02:51 s6-rc: info: service legacy-services successfully started

#

@sacred kelp

sacred kelp
#

nothing else?

tardy badger
#

no

sacred kelp
#

how do you start the container?

tardy badger
#

I used docker desktop

sacred kelp
#

on linux?

tardy badger
#

yes

#

ubuntu desktop

#

I tried using command line too

#

and protainer

#

no difference

sacred kelp
#

I'm not sure if this is setup correct then, you are far better off following the official install guide and use the cli

tardy badger
#

use the cli?

sacred kelp
#

docker run or docker compose

tardy badger
#

Tried that too

#

no difference

sacred kelp
tardy badger
#

[+] Running 1/1
⠿ Container homeassistant Started 6.1s

sacred kelp
#

and the ha log to it?

tardy badger
#

empty

sacred kelp
#

docker compose logs ?

tardy badger
#

homeassistant | s6-rc: info: service s6rc-oneshot-runner: starting
homeassistant | s6-rc: info: service s6rc-oneshot-runner successfully started
homeassistant | s6-rc: info: service fix-attrs: starting
homeassistant | s6-rc: info: service fix-attrs successfully started
homeassistant | s6-rc: info: service legacy-cont-init: starting
homeassistant | s6-rc: info: service legacy-cont-init successfully started
homeassistant | s6-rc: info: service legacy-services: starting
homeassistant | services-up: info: copying legacy longrun home-assistant (no readiness notification)
homeassistant | s6-rc: info: service legacy-services successfully started

sacred kelp
#

and what does netstat -tulpn say?

tardy badger
#

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:39461 0.0.0.0:* LISTEN 15806/com.docker.ba
tcp 0 0 127.0.0.1:6463 0.0.0.0:* LISTEN 121830/Discord --ty
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 616/systemd-resolve
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 766/cupsd
tcp6 0 0 ::1:631 :::* LISTEN 766/cupsd
udp 0 0 127.0.0.53:53 0.0.0.0:* 616/systemd-resolve
udp 0 0 0.0.0.0:631 0.0.0.0:* 1366/cups-browsed
udp 0 0 0.0.0.0:58146 0.0.0.0:* 663/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 663/avahi-daemon: r
udp6 0 0 :::36946 :::* 663/avahi-daemon: r
udp6 0 0 :::5353 :::* 663/avahi-daemon: r

sacred kelp
#

I dunno, your docker install might be borked or sth

tardy badger
#

Exactly same problem as me

#

however I turned off the firewall already

sacred kelp
#

not same problem

#

you need to stop follow random tutorials and commands and just try the official docs

tardy badger
#

i followed the officiak docs...

#

installed docker following docker's document

sacred kelp
#

yes and the problem lies in your docker install

#

which you've borked by installing docker desktop and whatnot

tardy badger
#

docker desktop is made by docker it's not a third party app

#

I will try again with no docker desktp and see what happens

sacred kelp
#

I've never said anything against that,
I just never needed to use it for homeassistant

tardy badger
#

like when I add port 8123 into the file I can connect to homr assistanr

#

but when it's network mode host it's not working