Need help with Home Assistant configuration on raspberry pi

This is my docker-compose file:

version: '3'
services:
  homeassistant:
    container_name: homeassistant
    image: "homeassistant/home-assistant"
    volumes:
      - /home/jm/Docker/home-assistant/home-assistant_config:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    restart: unless-stopped
    privileged: true
    network_mode: host

When I start it on my laptop that is connected to the router then I can go to
192.168.1.123:8123 (my current laptop IP ends with 123) and Home Assistant works like a charm.
But when I do the same on my rspberry pi (ip ends with 100) then I cant acces whe web Interface on 192.168.1.100:8123

when I run docker ps
sometimes container is running and sometimes it has status restarting

I usually start my copomos files with up -d
I checked without -d to see what is oing on.
There is:

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    | <jemalloc>: Unsupported system page size
homeassistant    | <jemalloc>: Unsupported system page size
homeassistant    | <jemalloc>: Unsupported system page size
homeassistant    | Fatal Python error: _PyRuntimeState_Init: memory allocation failed
homeassistant    | Python runtime state: unknown
homeassistant    | 
homeassistant    | [13:17:28] INFO: Home Assistant Core finish process exit code 1
homeassistant    | [13:17:28] INFO: Home Assistant Core service shutdown
homeassistant    | s6-rc: info: service legacy-services successfully started
homeassistant    | s6-rc: info: service legacy-services: stopping
homeassistant    | [13:17:29] INFO: Home Assistant Core finish process exit code 256
homeassistant    | [13:17:29] INFO: Home Assistant Core finish process received signal 15
homeassistant    | s6-rc: info: service legacy-services successfully stopped
homeassistant    | s6-rc: info: service legacy-cont-init: stopping
homeassistant    | s6-rc: info: service legacy-cont-init successfully stopped
homeassistant    | s6-rc: info: service fix-attrs: stopping
homeassistant    | s6-rc: info: service fix-attrs successfully stopped
homeassistant    | s6-rc: info: service s6rc-oneshot-runner: stopping
homeassistant    | s6-rc: info: service s6rc-oneshot-runner successfully stopped

But like I said. Even if it is running than I cant acces it throug the web

It seems that it was the main reason:

homeassistant    | <jemalloc>: Unsupported system page size
homeassistant    | <jemalloc>: Unsupported system page size
homeassistant    | <jemalloc>: Unsupported system page size
homeassistant    | Fatal Python error: _PyRuntimeState_Init: memory allocation failed
homeassistant    | Python runtime state: unknown

After changing the compose file to:

services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - ./hass_config:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    restart: unless-stopped
    privileged: true
    network_mode: host
    environment:
      DISABLE_JEMALLOC: "true"

Home Assistant started to work on RPI5
It was described here as an optimization and I didn’t check it before: