"Failure retrieving environments" for local stack after upgrade

[hobbes1069]

Ask a Question!

Full disclosure I'm on Fedora 41 using Podman with podman.socket service enabled.

# ll /var/run/docker.sock 
lrwxrwxrwx. 1 root root 23 Dec 13 12:01 /var/run/docker.sock -> /run/podman/podman.sock

I created a local stack using a compose and everything worked great. After upgrading to 2.21.4 and now 2.21.5 following the directions at https://docs.portainer.io/start/upgrade/docker and restarting the container it looks like everything was upgraded without error but I now get a string of errors basically stating it can't access the local environment.

I don't think it's relevant but here's the compose:

version: '3'

services:
  mosquitto:
    image: eclipse-mosquitto:latest
    container_name: mosquitto
    ports:
      - "1883:1883"
      - "9001:9001"  # WebSocket port
    volumes:
      - mosquitto_config:/mosquitto/config
      - mosquitto_data:/mosquitto/data
      - mosquitto_log:/mosquitto/log
    networks:
      - ming_network

  influxdb:
    image: influxdb:latest
    container_name: influxdb
    ports:
      - "8086:8086"
    environment:
      - INFLUXDB_DB=exampledb
      - INFLUXDB_ADMIN_USER=admin
      - INFLUXDB_ADMIN_PASSWORD=XXX
    volumes:
      - influxdb_data:/var/lib/influxdb
    networks:
      - ming_network

  nodered:
    image: nodered/node-red:latest
    container_name: nodered
    ports:
      - "1880:1880"
    volumes:
      - nodered_data:/data
    networks:
      - ming_network

  grafana:
    image: grafana/grafana:latest
    container_name: grafana
    ports:
      - "3000:3000"
    environment:
      - GF_SECURITY_ADMIN_PASSWORD=admin
    volumes:
      - grafana_data:/var/lib/grafana
    networks:
      - ming_network

networks:
  ming_network:
    driver: bridge

volumes:
  mosquitto_config:
  mosquitto_data:
  mosquitto_log:
  influxdb_data:
  nodered_data:
  grafana_data:

[hobbes1069]

Interestingly I can't load the logs either. It just stays grayed out, which makes me think it's a permission issue but I'm running Portainer as root and it was obviously able to access the volume to perform the updates.

[hobbes1069]

Turns out I just needed to add the --privileged option to Podman as SELinux was blocking access to some resources even running as root.