portainer: Recreating a container with new LTS gives 500 error

Before you start please confirm the following.

Problem Description

When trying to recreate a container I get and error: Request failed with status code 500 However, the container is recreated This only happened after the upgrade

Expected Behavior

A notice that the container was recreated successfully, and a recreated container

Actual Behavior

An error 500, but a recreated container

Steps to Reproduce

  1. Log in
  2. Choose Environment by clicking on it
  3. Choose Containers
  4. Choose container
  5. Click re-create
  6. Check to re-pull image
  7. Click recreate button
  8. See error 500 in the top right corner
  9. Click containers on the left
  10. Click the container again
  11. See the status of running for a few seconds

Portainer logs or screenshots

<html><body>   | Error | Failure | Unable to retrieve containers | 2024-08-27 11:59:48 -- | -- | -- | -- | --   | Error | Failure | Request failed with status code 500 | 2024-08-27 11:58:57   | Error | Failure | Request failed with status code 500 | 2024-08-27 11:50:12   | Error | Failure | Request failed with status code 403 | 2024-08-27 11:38:15   | Error | Failure | Request failed with status code 403 | 2024-08-27 11:38:04 </body> </html>

Portainer version

2.21.0

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Docker 24.0.7 (API: 1.43)

OS and Architecture

linux x86_64 Ubuntu 22.04.4 LTS

Browser

Firefox 129.0.2

What command did you use to deploy Portainer?

version: '3'
services:
  portainer-ee:
    container_name: Portainer-Compose
    hostname: portainer-compose
    image: portainer/portainer-ee:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /Data/Portainer/:/data
    ports:
      - 9000:9000
      - 9443:9443
    healthcheck:
      test: ['CMD', '/portainer', '--version']
      retries: 3
      interval: 30s
      timeout: 10s
    restart: always

Additional Information

I tested this through cloudflare tunnel, and swag (nginx) reverse proxy. Containers were not ones hosting the proxy.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 26 (6 by maintainers)

Most upvoted comments

About Synology

  • please open Feature Inquiry to have the Container Manager updated as soon as possible, here’s a nice guide with template to send.

i understand that you need to use the docker version 26/27, but, for example, at synology, the official docker has 24 version. . .

So… the docs still states that 2.21.1’s docker versions are: 26.0.2 and 27.0.1 (https://docs.portainer.io/start/requirements-and-prerequisites).

But this issue only happened on Docker 24 and below. Does this mean 24 is still ok with portainer 2.21.1?

On that page we also say:

The following tables list all of the configurations that we have tested, validated and consider to be functional. If a variant is not listed, it doesn’t mean it won’t work, it just means it hasn’t been tested.

Docker 26.0.2 and 27.0.1 are what we tested against in our automated and manual testing suites for the release. For this specific Docker 24 issue we of course tested against Docker 24. Where possible we recommend updating to a version of Docker that is not end-of-life, but understand that for Synology users in particular this is easier said than done.

So what’s the connection between #11882 and this one if this is not a duplicate of that one?

They are essentially duplicates, yes. The primary difference is the expected supported Docker versions for 2.21.0 LTS versus the 2.20.x release. For clarity, I will close #11882 as a duplicate of this.

@jamescarppe you, yourself indicated that the Expected Behavior is Container recreation to succeed.

Correct. We are discussing internally the next steps and I’ll report back here when I know more.

Can you please link Pull Requests with issues?

I believe #12178 is the PR for this. We’re in the process of adjusting our workflows in GitHub so I’ll raise this with the team.

And there are no commits between 2.21.0 and 2.21.1 tags: 2.21.1…2.21.0

Not sure why that’s not showing any. If I switch the order it shows the commits. https://github.com/portainer/portainer/compare/2.21.0...2.21.1

2.21.1 fixes the issue. Good to go, thank you.

Can you please link Pull Requests with issues?

And there are no commits between 2.21.0 and 2.21.1 tags: https://github.com/portainer/portainer/compare/2.21.1...2.21.0

The above comment asking you to download a file is malware to steal your account; do not under any circumstances download or run it. The post needs to be removed. If you have attempted to run it please have your system cleaned and your account secured immediately.