Failed loading environment The environment named local is unreachable.

[mikimause9]

Ask a Question!

Hi all,
I have been using Portainer for around a year. I recently did a complete format of my Linux server (since it got really messy) and started setting everything up from scratch. So, as docker is my main service ran on the machine, naturally second thing after installing it was to install portainer community edition. It worked... for a day or so. To be fair I have no idea what happened, I am not even sure did i do any system reboot for the last few hours (not counting debugging the problem itself). When I enter IPaddress.local:9443/ I see dashboard (after login) and I see my envoirement which shows "Up". But when I try to access it the icon changes from "Up" to "Down" and I see an error in right-upper corner "Failed loading environment The environment named local is unreachable." I tried slow by searching the issue, removing portainer and starting again while trying to change some env variable according to this and ended up on the 20-minutes long dialog with chatGPT which literally did nothing. I did try both docker run and docker compose file, tried removing any folder belinging associated with portainer. Please ask for any usefull information abt the system if not specified below, i dont really know what to put there.

OS: Debian GNU/Linux 13 (trixie) x86_64
Kernel: Linux 6.12.43+deb13-amd64

sudo docker logs portainer

2025/11/11 01:18AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:325 > encryption key file not present | filename=/run/secrets/portainer
2025/11/11 01:18AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:365 > proceeding without encryption key |
2025/11/11 01:18AM INF github.com/portainer/portainer/api/database/boltdb/db.go:137 > loading PortainerDB | filename=portainer.db
2025/11/11 01:18AM INF github.com/portainer/portainer/api/internal/ssl/ssl.go:79 > no cert files found, generating self signed SSL certificates |
2025/11/11 01:18AM INF github.com/portainer/portainer/api/chisel/service.go:228 > generated a new Chisel private key file | private-key=/data/chisel/private-key.pem
2025/11/11 01:18:20 server: Reverse tunnelling enabled
2025/11/11 01:18:20 server: Fingerprint haDg1BHSQkPl0SS2qSKT+K0OBFOHE2a6/G/YXmQUaC4=
2025/11/11 01:18:20 server: Listening on http://0.0.0.0:8000
2025/11/11 01:18AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:636 > starting Portainer | build_number=236 go_version=1.24.9 image_tag=2.33.3-linux-amd64 nodejs_version=18.20.8 version=2.33.3 webpack_version=5.88.2 yarn_version=1.22.22
2025/11/11 01:18AM INF github.com/portainer/portainer/api/http/server.go:367 > starting HTTPS server | bind_address=:9443
2025/11/11 01:18AM INF github.com/portainer/portainer/api/http/server.go:351 > starting HTTP server | bind_address=:9000
2025/11/11 01:18AM ERR github.com/portainer/portainer/api/internal/snapshot/snapshot.go:213 > the Podman environment option doesn't support Docker environments. Please select the Docker option instead. | error="the Podman environment option doesn't support Docker environments. Please select the Docker option instead." endpoint=local

(I know abt the last error with podman, but neither do I know why it's here, nor how to get rid of it. I tried selecting correct environment like a dozen times)

[jxxaxxy]

Same issue as you. It started when I updated my server tonight with latest docker 29.0. So there is either an issue with docker engine 29 or portainer isn't compatible with the newest version. Your screenshot shows Standalone 29.0.0. So same problem.

[Absolut-tech]

Oh thank god I thought I was going crazy, I even span up a brand new debian vm installed just docker and portainer updated and got the same error right off the bat. Definitely latest update broke something

[jxxaxxy]

Yeah and the worst part about it is. Someone post the issue after rc2 was released and the answer was to go back to an older version of 29.0 and that they don't look at beta versions to fix issues. So here we sit waiting on a fix ;-)

[devzwf]

so update to trixie ,
all is working fine with docker then tried portainer
oh my....... spend way to much time trying to debug this one to finally found this post....
it showing green

but as soon as you connect it failed with a status "2

[DjoeC]

Apparently an issue has been opened: #12925

Portainer is not using the minimum required Docker API 1.44 which has been around for a looooong time.

[jostrasser]

I am experiencing the same issue.

[Egrirt]

adding a +1 to this issue

[BigBaldyBoy]

same :/

[jaroslavGR]

Downgraded Docker from 29.0.0 to 28.5.2 and everything is working fine.

[liquidand]

can you point me on how to downgrade docker?

[devzwf]

I actually downgrade portainer to 2.20.2
much easier.

[Nurb4000]

Rolling back to 2.20.2 fixed it here too, thank you. I also thought i was going nuts, even removed docker, all my containers, etc..

[DaniMarques1]

Fixed. I just used this:

docker stop portainer docker rm portainer docker pull portainer/portainer-ce:2.20.2

docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.2

Thank you so much! Worked clean

[skrollme]

Fixed. I just used this:

docker stop portainer docker rm portainer docker pull portainer/portainer-ce:2.20.2

docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.2

Thanks, but to be honest: This is no fix. It is a rollback to a version which is not affected :D Portainer still has to fix their stuff in terms of "adapting to newer docker API versions"

[Nurb4000]

Agreed, its not a true 'fix' and only a 'workaround', but it gets things working until they can update to the latest API, and we can stay on latest docker in the meantime, which i think is a better idea than rolling back docker as the workaround. ( security, effort, risk, bla bla )

[piotr-kubica]

Thanks! This works! Chatgpt couldn't solve the problem.

[ngoun]

same issue on Ubuntu 22.04.3

[Nick-Portainer]

Duplicate - #12925

Hello everyone, this is a RC release from Docker. We are aware of breaking changes for Docker 29 but please stick to the tested versions of Docker found here - https://docs.portainer.io/start/requirements-and-prerequisites

[punksinatra]

having the same issue after the latest docker update

[skrollme]

Same for me. Portainer is still broken with non-RC docker 29.0.2 (Build 8108357)

[ptr727]

Same for me, updated docker release channel on debian, now this error.

[aizazmueez]

same for me

[mathieukergosien]

Same here...

[isaacnewtonfx]

I also hit the same problem today. Wasted all my time.

This solution worked for me

#12925 (comment)

[romanad]

Have same issue

[SaschaN71]

As Workaround I used

systemctl edit docker.service

and added

[Service]
Environment=DOCKER_MIN_API_VERSION=1.24

[guerreroares]

thaks, is okey very thanks

[luisriverag]

As Workaround I used

systemctl edit docker.service

and added

[Service]
Environment=DOCKER_MIN_API_VERSION=1.24

Thanks, worked for me with Ubuntu 22 & 24

[kristjannomm]

Thanks!!

[Jaccobird]

Thank you worked like a charm!!

[phillipc]

Thanks, it works with Portainer 2.35.0 STS. Here is some context: https://www.docker.com/blog/docker-engine-version-29/

[tirkk]

I'm also having the same problem (Failed loading environment
The environment named local is unreachable.) with Community Edition 2.33.4 LTS on Ubuntu 24.04.3 LTS on Docker Engine - Community
Version: 29.0.2

:(

The cause or reason for this problem is currently unknown.?

[PizzaProgram]

Did you read this... (link) solution to the end from a week ago?

[bcutter]

Oh dear what a major f***up. Spent an hour before discovering this and #12925. This should have been handled more nicely... now thousands of users run into this, great.

#12925 (comment) did the trick - even it is more a workaround right.

[euroegyptn]

+1

[rookyy]

+1

[6502c]

+1 (and that's an upper case 1)

[PizzaProgram]

Just 2 more thinks:

1. Failed Loading Environment #12925 (comment) did the trick both at:

• Community Edition 2.33.4 LTS and
• Community Edition 2.21.5 LTS

on Debian GNU/Linux 11 (bullseye)

2. When I've told ChatGPT: it failed to point me to the right solution, this was the answer:
   Link ...

Summary:

it suggests me to add this line to portrainer's yaml:

services:
  portainer:
    image: portainer/portainer-ce:latest
    user: root
...

With the extra line: user: root Portainer would run as UID 0 inside the container → guaranteed permission to access the Docker socket, regardless of outside system UID/GID changes.

is this correct ?

[devzwf]

Nope

[mspitb]

The same issue.

[adirt4289]

Same here

[ruijmm]

DEFINITIVE SOLUTION: Portainer + Docker Engine v29

🎯 PROBLEM IDENTIFIED

Docker Engine v29 introduced incompatibility with Portainer v2.33.4 due to the minimum API increase from 1.41 to 1.44.

Symptoms:

• ✅ Portainer starts normally
• ❌ Environment "primary" appears as "Down" and "Disconnected"
• ❌ Error: "Failed loading environment - The environment named primary is unreachable"
• 🔍 This can happen on some Cloud VMs: Hetzner, Digital Ocean, AWS EC2, etc.

🔧 IMPLEMENTED SOLUTION

1. Docker Daemon Configuration

Created /etc/docker/daemon.json:

{
  "min-api-version": "1.24",
  "log-driver": "json-file", 
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "features": {
    "containerd-snapshotter": false
  }
}

2. Restart Docker

sudo systemctl restart docker

3. Verify Compatibility

docker version
# Should show: API version 1.52 (minimum version 1.24)

📚 REFERENCE

• Docker Engine v29 Blog Post
• Specific issue: Minimum API Version Update (1.44)
• Solution: Override minimum API version to 1.24

[manjump]

Good morning,

I had the same problem so I downgraded docker. And now, Impossible to access stacks:

Have you an idea please?

[valorisa]

Damned !

[SKJoy]

Downgrading Portainer to 2.20.2 is a much safer approach than downgrading Docker itself.

[manjump]

OK but the same problem:

[SKJoy]

OK but the same problem:

You can't say that is a SAME problem. We are dealing with the local Docker connection here.

[manjump]

I don't understand what you say

[Come-sr]

I don't understand what you say

Basically you get this error because the stack / container was created outside of portainer (or outside the portainer you're currently running)

[manjump]

So precisely, originally, I created all my containers with the stacks. Then I proceeded to carry updates portainer and no worries. Only now, after the portainer update in 2.33.4 then downgrade to 2.20.2, I no longer have access to the stacks.

[mavorse]

How disrespectful do you have to be to leave your users completely in the dark? Portainer clearly doesn’t care . Great job, Portainer , really shows how much you “value” your users. People have wasted hours trying to figure out what’s wrong, and they don’t even acknowledge the issue. This thread is two weeks old, and the official documentation still doesn’t mention that the current version is incompatible with the latest Docker. Instead, people wasted hours chasing a problem that should’ve been openly communicated. Two weeks have passed and the official installation guide still doesn’t even hint at the incompatibility with the latest Docker.

[Nick-Portainer]

@mavorse We have acknowledged the issue and are providing updates here: https://github.com/orgs/portainer/discussions/12928, as well as on Reddit (https://www.reddit.com/r/portainer/comments/1oumupa/docker_29_is_currently_not_compatible_with/) and in our Slack channel.

We’ve also emailed all 3-Node Free and Business users.

I’ve mentioned that a fix is planned for this month. I can’t confirm exact dates, but it will be included in our regular STS release cycle, followed by LTS. It wasn’t included in the previous update due to an existing code freeze, and since there is a working workaround, it will be delivered in the next STS patch.

We appreciate your patience. We’re not leaving anyone in the dark, the issue, workaround, and release plan have all been communicated.

[Nick-Portainer]

Locking due to duplicate and noise - Please look here for workaround and community comms - #12925