Failed loading environment on Umbrel

[DaniilL12321]

portainer does not work after reboot Umbrel

Failed loading environment
The environment named primary is unreachable.

Error:
2025/03/07 02:27PM WRN [github.com/portainer/portainer-ee/api/docker/local.go:83](http://github.com/portainer/portainer-ee/api/docker/local.go:83) > failed to clean up updater stack | error=“failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” retry time=0

[Nick-Portainer]

Hi @DaniilL12321 I believe Umbrel have some custom config for running Portainer as well as Docker engine so unless you are running Portainer outside of Umbrel and using our documented deployment method it's going to be difficult to assist you.

This line Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” retry time=0 is important to check, is Docker working on your machine and does it have the correct permissions to access the Docker daemon

[DaniilL12321]

Hi @DaniilL12321 I believe Umbrel have some custom config for running Portainer as well as Docker engine so unless you are running Portainer outside of Umbrel and using our documented deployment method it's going to be difficult to assist you.

This line Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” retry time=0 is important to check, is Docker working on your machine and does it have the correct permissions to access the Docker daemon

I install portainer from stock app store. By first start portainer after installing, all good. But if I reboot my raspberry pi with Umbrel occurs this error. If I delete app and install his again, that all working to next reboot rpi. But I have it again configure all stacks and settings

Docker exactly correct working on my machine, otherwise even portainer would doesnt working

here is docker compose, which used

docker-compose.yml:

version: '3.7'
services:
  app_proxy:
    environment:
      APP_HOST: portainer_portainer_1
      APP_PORT: 9000
    container_name: portainer_app_proxy_1
  docker:
    image: >-
      docker:27.2.0-dind
    privileged: true
    network_mode: host
    stop_grace_period: 1m
    restart: on-failure
    environment:
      DOCKER_ENSURE_BRIDGE: dind0:10.32.0.1/16
    entrypoint: /entrypoint.sh
    command: |
      dockerd
        --bridge dind0
        --data-root /data/data
        --exec-root /data/exec
        --host unix:///data/docker.sock
        --pidfile /data/docker.pid
    volumes:
      - ${APP_DATA_DIR}/entrypoint.sh:/entrypoint.sh
      - ${APP_DATA_DIR}/data/docker:/data
    container_name: portainer_docker_1
  portainer:
    image: portainer/portainer-ee
    command: '--host unix:///var/run/docker.sock --admin-password-file=/default-password'
    restart: on-failure
    volumes:
      - ${APP_DATA_DIR}/default-password:/default-password
      - ${APP_DATA_DIR}/data/portainer:/data
      - ${APP_DATA_DIR}/data/docker:/var/run
    container_name: portainer_portainer_1

entrypoint.sh:

#!/bin/sh

# This hack can be removed if https://github.com/docker-library/docker/pull/444 gets merged.

# Remove docker pidfile if it exists to ensure Docker can start up after a bad shutdown
pidfile="/var/run/docker.pid"
if [[ -f "${pidfile}" ]]
then
    rm -f "${pidfile}"
fi

# Use nftables as the backend for iptables
for command in iptables iptables-restore iptables-restore-translate iptables-save iptables-translate
do
    ln -sf /sbin/xtables-nft-multi /sbin/$command
done

# Ensure that a bridge exists with the given name
ensure_bridge_exists() {
    local name="${1}"
    local ip_range="${2}"

    # Check if the bridge already exists
    if ip link show "${name}" &>/dev/null
    then
        echo "Bridge '${name}' already exists. Skipping creation."
        ip addr show "${name}"
        return
    fi

    echo "Bridge '${name}' does not exist. Creating..."
    ip link add "${name}" type bridge
    ip addr add "${ip_range}" dev "${name}"
    ip link set "${name}" up

    echo "Bridge '${name}' is now up with IP range '${ip_range}'."
    ip addr show "${name}"
}

if [[ "${DOCKER_ENSURE_BRIDGE}" != "" ]]
then
    bridge="${DOCKER_ENSURE_BRIDGE%%:*}"
    ip_range="${DOCKER_ENSURE_BRIDGE#*:}"
    ensure_bridge_exists "${bridge}" "${ip_range}"
fi

exec dockerd-entrypoint.sh $@

Judging by logs, error occurs in docker:27.2.0-dind

Bridge 'dind0' already exists. Skipping creation.
48: dind0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
    link/ether 9e:1d:1f:78:08:9a brd ff:ff:ff:ff:ff:ff
    inet 10.32.0.1/16 scope global dind0
       valid_lft forever preferred_lft forever
    inet6 fe80::b011:50ff:fede:86b7/64 scope link 
       valid_lft forever preferred_lft forever
cat: can't open '/proc/net/ip6_tables_names': No such file or directory
cat: can't open '/proc/net/arp_tables_names': No such file or directory
iptables v1.8.10 (nf_tables)
time="2025-03-09T12:06:21.789685721Z" level=info msg="Starting up"
failed to start daemon, ensure docker is not running or delete /data/docker.pid: process with PID 33 is still running

I tried to fixed with ChatGPT (deleting docker.pid, image and other actions), but his response not working ideas from fixing this error🙁

[DaniilL12321]

To me succeeded fix this problem by removing docker dind from docker-compose and connect docker.sock directly

After reboot now good working

Maybe someone also come in handy

fixed docker-compose.yml

version: '3.7'
services:
  app_proxy:
    environment:
      APP_HOST: portainer_portainer_1
      APP_PORT: 9000
    container_name: portainer_app_proxy_1

  portainer:
    image: portainer/portainer-ee
    command: '--host unix:///var/run/docker.sock --admin-password-file=/default-password'
    restart: on-failure
    volumes:
      - ${APP_DATA_DIR}/default-password:/default-password
      - ${APP_DATA_DIR}/data/portainer:/data
      - /var/run/docker.sock:/var/run/docker.sock
    container_name: portainer_portainer_1

If someone using Community Edition replace image portainer/portainer-ee on portainer/portainer-ce

[DaniilL12321]

Why did it happen out of nothing, everyone was sleeping by that time??

I dont know, maybe, if you used Umbrel, that this problem simply exists out of the box. And you fixing replacement docker-compose on my

If you dont used Umbrel, its hard to understand by this log. May to try delete docker.pid and checked permissions for docker.sock

[Maxxxel]

I'm using umbrel for 2 months now and everything runs smoothly since, but this morning I woke up with this error. Haven't touched the system and restart doesn't fix it.

[Maxxxel]

Had this error again this morning, what is this???

[DaniilL12321]

Had this error again this morning, what is this???

I don`t know. After that moment I have not experienced this error

[baukeposthuma]

For me, removing Docker dind fixes the issue. However after rebooting Umbrel, all running containers in the Docker sock will be removed.