"serv status" Value error

serv is adding and removing services properly but status check fails.
Not sure if it's related to specific process or in general

ubuntu@ip-172-31-26-123:~$ sudo serv status
INFO - Retrieving status...
Traceback (most recent call last):
File "/usr/local/bin/serv", line 9, in
load_entry_point('Serv==0.1.0', 'console_scripts', 'serv')()
File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 716, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 696, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 1060, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 889, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/serv/serv.py", line 408, in status
status = Serv(init_system, verbose).status(name)
File "/usr/local/lib/python2.7/dist-packages/serv/serv.py", line 193, in status
return init.status(name)
File "/usr/local/lib/python2.7/dist-packages/serv/init/upstart.py", line 53, in status
svcs_info = [self._parse_service_info(svc) for svc in svc_list]
File "/usr/local/lib/python2.7/dist-packages/serv/init/upstart.py", line 64, in _parse_service_info
last_action, status = s[1].split('/')
ValueError: need more than 1 value to unpack

Found out this doesn't happen on Centos...

[centos@ip-172-31-32-233 ~]$ sudo serv status vault
INFO - Retrieving status...
{
"init_system": "systemd",
"init_system_version": "default",
"services": []
}

status is currently broken, as stated in the README. I will be working on it once Serv is stable enough on other fronts and once it supports most major init systems so that I can provide a unified status experience.


Is there a way to do associations with appFactories?

Something like? Or some other pattern..
const user = await cy.appFactories([
  ['create', 'user', { username: testUserName }],
])

cy.appFactories([
   ['create', 'post', {user: user }],
])

@stoplion I think you meant to post this to https://github.com/shakacode/cypress-on-rails/.


Trapping Rainwater

I would like to add the Trapping Rainwater problem's solution in c++. I will also add the time,space complexities to it. Please assign this issue to me.

Hey @Rishika30 can you please elaborate a bit more on your approach and also tell us whether you are working under Gssoc as a participant?

Yes I am a Gssoc'21 participant. I will use two pointer approach to solve it in which rainwater stored at each index is difference between min(left_max height,right_max height) and height of cuurent index.

@Rishika30 I didn't get your approach Can you add bit more how you are going to implement and add the same thing in the description as well!

@ankitaggarwal23 Two pointers will be there left and right initialised with 0 and n-1. And left_max,right_max also as 0. Then start iterating the array by comparing whether l<=r. If array[left]<array[right] then see if array[left]>=left_max and if that is true then update left_max with array[left] otherwise it means that some water will be trapped in that index as some height on left to that particular index and some height to right of that index are greater than height of that index. And it can be calculated by result+=max_left- array[left]. And then do left++ . If array[left]>array[right] then we compare and see if array[right]>=right_max and if true, update right_max. Else some water will be trapped which is calculated by result+=right_max-array[right] and do right--.

I am a GSSOC'21 participant and want to work on issue.
I can provide the code in C++ with proper comment description .
please assign me this issue.

I am a GSSOC'21 participant and want to work on issue.
I can provide the code in C++ with proper comment description .
please assign me this issue.

@neha030 Actually @Rishika30 is already working on C++. So Can you select any other language you want to work?
You can open a new issue with the same concept but with implementation in a different programming language. We will assign it to you then. Happy Coding!😊

@ankitaggarwal23, sir I can solve this problem in python,
The approach is using two pointers,
First initialize left pointer to 0 and right pointer to size-1
Till left<right  , will update left_Max and right_Max with max(left_Max, height[left]) and max(right_Max, height[right])
update total water trapped according to left_Max and right_Max
Time complexity: O(n)
Space complexity: O(1)
@ankitaggarwal23, thank you for your time and consideration, kindly assign this to me.

@ankitaggarwal23 I have added the file and created pull request #2928 but it is showing one check was not successful Deepsource java(beta) one. Could you please tell if it is alright or not


Unable to retrieve image details or access container console after update of Docker to v26

EDIT FOR TLDR (April 5, 2024)
Portainer 2.20.1 has now been released, which includes a fix for these issues under Docker 26. We recommend updating to 2.20.1 if you need to use Docker 26.

Original report
Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
Inability to see image information and to use container consoles.
Expected Behavior
Image info is accessible and container consoles are functional
Actual Behavior
Clicking on an image causes the error message "Error Unable to retrieve image details" and clicking on container consoles also produce this same error.
Steps to Reproduce

SSH into host server
apt update && apt upgrade
(Update updates docker-ce alongside any dependencies)

Portainer logs or screenshots
No response
Portainer version
2.19.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker 5:26.0.0-1~ubuntu.20.04~focal
OS and Architecture
Ubuntu 22.04
Browser
No response
What command did you use to deploy Portainer?
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:latest

Additional Information
Info seen online for this issue states to execute the following for recreating the portainer container:
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce:latest
This does not work, and the issue persists even after a reinstall of Ubuntu and reinstall of docker/portainer.
Only feasible fix is to rollback docker-ce version.

Same here, it may be related to Docker Swarm 26.0.0

This is indeed an issue with Docker 26 compatibility - this version removed some functionality we rely on to display the image details. As Docker 26 has only just come out we were unable to test against it for any past releases, but I am discussing with the team as to our next steps.

Same issue.

Same here when accessing console for any container in Portainer BE

Here as well!

and how do I revert the docker version? If not, how do I install a more stable version?

and how do I revert the docker version? If not, how do I install a more stable version?

Docker provides instructions for installing specific versions - these are the instructions for Ubuntu (select the Specific version tab in step 2) but there are other installation processes available for other distros. 25.0.5 is the most recent version in the version 25 release. For example, on a Ubuntu 20.04 server:
VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal
sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

If you're running ubuntu 22.04, then set the version as follows.
VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy
Rolling back makes console etc available again.

For ubuntu 22.04, the correct version should be
VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy

I also spot that when I click on the image sha link in the images list page, it refreshes a bit and returns to the same list page.
I'm still using Debian 10 in my old server. Base on the info above, I revert to docker-ce v25 and confirm it works now.
sudo apt install docker-ce=5:25.0.5-1~debian.10~buster

I have AlmaLinux 8 as my OS. The instructions for downgrading are in the Specific version tab at https://docs.docker.com/engine/install/centos/
So I did it like this:
  dnf -y install docker-ce-25.0.5-1.el8 docker-ce-cli-25.0.5-1.el8

Then my Portainer Business Edition 2.19.4 the exec console started working again.

The same problem for Debian 12 - another one also when uploading Portaine with docker stack deploy -c portainer.yaml portaine message: (Since --detach=false was not specified, tasks will be created in the background. In a future release, --detach=false will become the default.) I worked around it with: docker stack deploy --detach=false -c portainer.yaml portainer

Same problem here "Inability to see image information and to use container consoles" for Portainer BE  on Ubuntu 23.10

Same issue here

Same issue here!

Debian Bookworm here... no console access. Seems like the image update indicator (red/green) is also affected, as all containers are "green"... very unusual. To work around I did this (borrowing from ubuntu above):
VERSION_STRING=5:25.0.5-1~debian.12~bookworm
sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
'''

debian 12 fresh install
Docker version 26.0.0, build 2ae903e
Portainer Business Edition 2.19.4

same here:
openmediavault --> compose --> nginx
openmediavault --> compose --> portainer
previously used portainer console to access nginx to rsync index.html file, but now no longer able to.

Have the same problem but only when connected to the x86 version of the agent on my machines (1 ARM / 1 x86_64).
Does the docker version have to do something with it beeing unable to connect to the image?
Versions:
Portainer CE 2.19.4 - (Running on the ARM Server but connected through the Agent)
Agent v 2.19.4 - (Same on all machines)
ARM Server:
Ubuntu 23.10
Docker 25.0.2
x86 Server:
Ubuntu 22.04.4
Docker 26.0.0

Same problem here. Any ETA by when we can expect a fix? It's quite annoying to not be able to get into a container's shell from the browser. 😉

For now I have downgraded to docker 25.0.5 by apt removing and auto cleaning docker. Then using dockers install script with the —version tag. Then commenting out docker from its sources.list.d until there’s a fix

For now I have downgraded using following command and i am back in business. Will not upgrade these 3 packages until i see a fix here.
sudo apt-get install docker-ce=5:25.0.5-1~raspbian.11~bullseye docker-ce-cli=5:25.0.5-1~raspbian.11~bullseye docker-ce-rootless-extras=5:25.0.5-1~raspbian.11~bullseye

I have AlmaLinux 8 as my OS. The instructions for downgrading are in the Specific version tab at https://docs.docker.com/engine/install/centos/
So I did it like this:
  dnf -y install docker-ce-25.0.5-1.el8 docker-ce-cli-25.0.5-1.el8

Then my Portainer Business Edition 2.19.4 the exec console started working again.

This one worked for me:
sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.11~bullseye

same here:
debian 12
Docker version 26.0.0, build 2ae903e
Portainer Business Edition 2.19.4

I also spot that when I click on the image sha link in the images list page, it refreshes a bit and returns to the same list page. I'm still using Debian 10 in my old server. Base on the info above, I revert to docker-ce v25 and confirm it works now. sudo apt install docker-ce=5:25.0.5-1~debian.10~buster

This one did the job for my version of debian:
sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.11~bullseye

I also spot that when I click on the image sha link in the images list page, it refreshes a bit and returns to the same list page. I'm still using Debian 10 in my old server. Base on the info above, I revert to docker-ce v25 and confirm it works now. sudo apt install docker-ce=5:25.0.5-1~debian.10~buster

This one did the job for my version of debian:
sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.11~bullseye

big thanks, it works!
sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.12~bookworm

for ubuntu 23.10 the command below works:
VERSION_STRING=5:25.0.5-1~ubuntu.23.10~mantic sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

Commenting to help others and to get visibility to quickly fix this issue.
For Ubuntu 20.04 Focal Fossa use this command to fix the issue by downgrading docker
VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal
sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
As others have suggested commenting out docker from the sources.list until there’s a fix may be a good idea since any time you run an apt update or apt-get update this will update docker again.
Alternatively you can set a hold on the packages by running "sudo apt-mark hold docker-ce docker-ce-cli docker-ce-rootless-extras containerd.io docker-buildx-plugin docker-compose-plugin"
To undo the hold run "sudo apt-mark unhold docker-ce docker-ce-cli docker-ce-rootless-extras containerd.io docker-buildx-plugin docker-compose-plugin"

same here:
openmediavault --> compose --> nginx
openmediavault --> compose --> portainer
previously used portainer console to access nginx to rsync index.html file, but now no longer able to.
Now have to ssh into OMV and run:
chris@omv:~$ docker exec -it [nginx container ID] /bin/bash
I then do the rsync from within the container.

VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

Getting this error -
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

Package docker-ce-rootless-extras is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '' for 'docker-ce' was not found
E: Version '' for 'docker-ce-cli' was not found
E: Version '' for 'docker-ce-rootless-extras' was not found

VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

Getting this error -
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

Package docker-ce-rootless-extras is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '' for 'docker-ce' was not found
E: Version '' for 'docker-ce-cli' was not found
E: Version '' for 'docker-ce-rootless-extras' was not found

Which version of ubuntu are you using ? can you run lsb_release -a to see if you are using the proper package version ?

Same error here too... just when it's time to update everything... I'd rather wait for an update to fix it than to revert a version, I hope it arrives quickly

I am so glad this issue was not my networking configuration.
I will be watching this thread for updates and information, I am as well seeing this issue.

got the same error on omv 7 running portainer after updating to 26 used sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.12~bookworm to downgrade works like charm! wont update docker until support for 26 is out.

Same boat as everyone else running Portainer
I'm still using OVM 6 on Bullseye needed to downgrade to docker-ce (5:25.0.5-1~debian.11~bullseye)
"sudo apt install --allow-downgrades docker-ce=5:25.0.5-1~debian.11~bullseye"

VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

I am using jammy
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.4 LTS
Release:	22.04
Codename:	jammy

I updated the command to
VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING docker-ce-rootless-extras=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
but got above error.

Same happening for me on Ubuntu 22.04, Docker 26.0. Fix from @gsanchez2004 worked.
For anyone getting issues:
Checking the OS version first.
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Then, said fix.
$ VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy
$ sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

And expected output:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
containerd.io is already the newest version (1.6.28-2).
docker-buildx-plugin is already the newest version (0.13.1-1~ubuntu.22.04~jammy).
docker-compose-plugin is already the newest version (2.25.0-1~ubuntu.22.04~jammy).
Suggested packages:
  cgroupfs-mount | cgroup-lite
The following packages will be DOWNGRADED:
  docker-ce docker-ce-cli
0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 2 not upgraded.
Need to get 27.3 MB of archives.
After this operation, 3411 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 https://download.docker.com/linux/ubuntu jammy/stable arm64 docker-ce-cli arm64 5:25.0.5-1~ubuntu.22.04~jammy [12.4 MB]
Get:2 https://download.docker.com/linux/ubuntu jammy/stable arm64 docker-ce arm64 5:25.0.5-1~ubuntu.22.04~jammy [14.9 MB]
Fetched 27.3 MB in 3s (9362 kB/s)
dpkg: warning: downgrading docker-ce-cli from 5:26.0.0-1~ubuntu.22.04~jammy to 5:25.0.5-1~ubuntu.22.04~jammy
(Reading database ... 121309 files and directories currently installed.)
Preparing to unpack .../docker-ce-cli_5%3a25.0.5-1~ubuntu.22.04~jammy_arm64.deb ...
Unpacking docker-ce-cli (5:25.0.5-1~ubuntu.22.04~jammy) over (5:26.0.0-1~ubuntu.22.04~jammy) ...
dpkg: warning: downgrading docker-ce from 5:26.0.0-1~ubuntu.22.04~jammy to 5:25.0.5-1~ubuntu.22.04~jammy
Preparing to unpack .../docker-ce_5%3a25.0.5-1~ubuntu.22.04~jammy_arm64.deb ...
Unpacking docker-ce (5:25.0.5-1~ubuntu.22.04~jammy) over (5:26.0.0-1~ubuntu.22.04~jammy) ...
Setting up docker-ce-cli (5:25.0.5-1~ubuntu.22.04~jammy) ...
Setting up docker-ce (5:25.0.5-1~ubuntu.22.04~jammy) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Restarted the Portainer container and I am able to access my container's shell now.

sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

stil getting error
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce' was not found
E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce-cli' was not found

As Docker 26 has only just come out we were unable to test against it for any past releases

@jamescarppe Do you have any CI pipelines that run when your third-party integrations (such as https://hub.docker.com/_/docker) publish new releases?

sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

stil getting error
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce' was not found
E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce-cli' was not found

I set the version directly in the command (assuming that I made a syntax mistake and it worked fine.
sudo apt-get install docker-ce=5:25.0.5-1~ubuntu.22.04~jammy docker-ce-cli=5:25.0.5-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin

In case it helps anyone, I downgraded my docker but of course the next time I ran an apt upgrade it tried to upgrade them.  To stop this I pinned the docker versions - I'm on Ubuntu, the same should work for Debian but other distros will have different way's of pinning (unless they're based on Debian/Ubuntu).  This is for the Jammy release:
sudo bash -c 'cat > /etc/apt/preferences.d/docker' << EOF
Package: docker-ce*
Pin: version 5:25.0.5-1~ubuntu.22.04~jammy
Pin-Priority: 999
EOF

To remove the pin, delete the file.

FYI just notified there is a new updated version for docker apps apt repository: 26.0.0-1. Has anyone tried ?
I'm currently away my nodes, so i can not try my self and feedback.

sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

stil getting error
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce' was not found
E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce-cli' was not found

Are you using the Docker repositories ? it should work , anyway i saw @asymetricbalance replaced directly the command using the needed version and it worked for him :
sudo apt-get install docker-ce=5:25.0.5-1~ubuntu.22.04~jammy docker-ce-cli=5:25.0.5-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin

Having the same, also my IPVLAN network in docker doesn't resolve names anymore, so no internet access for my dockers since the update. Updated 2 machines with OMV-Portainer, same problem with both of them instantly after the update.

sudo apt-get install docker-ce=5:25.0.5-1~ubuntu.22.04~jammy docker-ce-cli=5:25.0.5-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin
Yes that's the temporary way go till resolution, probably a new Portainer version ...... if I clearly understand, as mentioned here: https://github.com/portainer/portainer/issues/11436#issuecomment-2011713567

Swarm 26.0.0
portainer/agent:2.19.4
portainer/portainer-ce:2.19.4
CentOS Stream release 9
When I use Portainer console to log in to the container.
Error
Unable to retrieve image details

getting the package not found error.  Any thoughts on what I'm doing wrong?:
dan@DockerHost:~$ VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy
sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce' was not found
E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce-cli' was not found

getting the package not found error. Any thoughts on what I'm doing wrong?:
dan@DockerHost:~$ VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy
sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-ce-cli

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  docker-buildx-plugin

E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce' was not found
E: Version '5:25.0.5-1~ubuntu.22.04~jammy' for 'docker-ce-cli' was not found

Try using directly :
sudo apt-get install docker-ce=5:25.0.5-1~ubuntu.22.04~jammy docker-ce-cli=5:25.0.5-1~ubuntu.22.04~jammy containerd.io docker-buildx-plugin docker-compose-plugin

if it doesn´t work check if you are using the proper Docker repositories
Best regards !

I also have the same error, I can't access portainer as I always did in other installations with Docker, this time it doesn't open and gives a 404 error.

The question is, is it fixable from the Portainer or Docker side?

Please read the thread , the problem arose with the last version of docker if you move to the previous to the last portainer will work fine.

So? Did you check Docker's release notes? Maybe they changed it on purpose and Portainer needs to be changed now as well. 🤷

The question is, is it fixable from the Portainer or Docker side?

Please read the thread , the problem arose with the last version of docker if you move to the previous to the last portainer will work fine.

so portainer is no longer compatible with docker.

Portainer seems to have some issues with the last docker version, so i think until the issue is solved, at least in my case, i can deal with use of the previous version. If its not solved soon i will have to look for another docker manager to replace Portainer.

25.0.5

in my case Docker version 25.0.5 worked like a charm.

it makes sense: #11434 - so docker 24 is the last that might be compatible.

Docker version 25.0.5

Having some trouble since the latest upgrade and downgrading to 25.0.5 on one machine running portainer again. 1cpu spikes to 100% while pulling an image therefore it's impossible slow, not sure if that's portainer related or not, someone else having that issue?

on raspberry with official OS
VERSION_STRING=5:25.0.5-1~debian.12~bookworm
apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

Looking a bit at the issue, it seems to be that it's due to the deprecated "Container and ContainerConfig fields in Image inspect" which got removed in v26: https://github.com/docker/cli/blob/v26.0.0/docs/deprecated.md#container-and-containerconfig-fields-in-image-inspect
This feature was already deprecated in Docker v25 (Released in January) and was due for removal for v26. A fix is also provided in the documentation. Somebody dropped the ball here.

The most recent version of the 2.19 branch (2.19.4) was released in December, prior to the Docker 25 release that contained the deprecation notice for this functionality. As such it was not tested against Docker 25 or Docker 26 as neither was released at the time.
We're currently working on a fix for this issue which we intend to roll out in our next patch release.

2.20 is based off 2.19.4 and was also not built with Docker 26 support (2.20.0 was released just before Docker 26 was).

Having the same, also my IPVLAN network in docker doesn't resolve names anymore, so no internet access for my dockers since the update. Updated 2 machines with OMV-Portainer, same problem with both of them instantly after the update.

I also was having DNS issues. Downgrading Docker to 25 fixed images issue but DNS one persisted. Rolled back to Docker 24 - and DNS started to work without a hassle
Armbian (Debian)
apt install --allow-downgrades docker-ce=5:24.0.9-1~debian.12~bookworm

Having the same, also my IPVLAN network in docker doesn't resolve names anymore, so no internet access for my dockers since the update. Updated 2 machines with OMV-Portainer, same problem with both of them instantly after the update.

I also was having DNS issues. Downgrading Docker to 25 fixed images issue but DNS one persisted. Rolled back to Docker 24 - and DNS started to work without a hassle
Armbian (Debian)
apt install --allow-downgrades docker-ce=5:24.0.9-1~debian.12~bookworm

Thanks man!!!! Worked!!!

We've just pushed out a MOTD update (which you'll see in-app when you next log in) which links to our new blog post on the topic. We'll be updating the blog post (and this thread) as the fix proceeds.

for those like myself who don't know, for ubuntu and debian style systems this will allow all other upgrades to happen except the docker upgrade
apt-mark hold docker-ce*

for those like myself who don't know, for ubuntu and debian style systems this will allow all other upgrades to happen except the docker upgrade
apt-mark hold docker-ce*

@Rob-bb
and How can I roll back the update?
Thanks

Hi guys, I don't understand if we should expect a fix from Docker or Portainer.
Thanks in advance
PC

@Rob-bb and How can I roll back the update? Thanks

Scroll up the page there are several examples

Hi guys, I don't understand if we should expect a fix from Docker or Portainer. Thanks in advance PC

Please read here https://www.portainer.io/blog/portainer-and-docker-26

Hi guys, I don't understand if we should expect a fix from Docker or Portainer. Thanks in advance PC

Please read here https://www.portainer.io/blog/portainer-and-docker-26

Thank you

Centos7 system temporarily returns to normal after being rolled back using the following command:
yum downgrade --setopt=obsoletes=0 -y docker-ce-25.0.5-1.el7 docker-ce-cli-25.0.5-1.el7 containerd.io

Installed portainer ce 2.20.0 and updated docker to version 26 , unfortunately problem remains
i get "Unable to retrieve image details" when trying to see image details and not able to get into console either

Facing the same issue on ubuntu 22.04. The given solution fixed it for me

I also spot that when I click on the image sha link in the images list page, it refreshes a bit and returns to the same list page. I'm still using Debian 10 in my old server. Base on the info above, I revert to docker-ce v25 and confirm it works now. sudo apt install docker-ce=5:25.0.5-1~debian.10~buster

This issue return upon version 2.20.0

This issue return upon version 2.20.0

From the Poratiner itself :

Latest News From Portainer
We are aware of compatibility issues with all versions of Portainer and Docker 26. Our team is working on fixes for the issues, with a 2.20.1 patch in testing, and we recommend against updating to Docker 26 at this time. You can find out more in our blog post Portainer and Docker 26.

So, we have to wait until 2.20.1 for the resolution.

@gsanchez2004
Does anyone know when the version 2.20.1  will be released
Thanks

Portainer 2.20.1 has now been released, which includes a fix for these issues under Docker 26. We recommend updating to 2.20.1 if you need to use Docker 26.

@jamescarppe
I tried pulling the portainer/portainer-ce latest image but I get nothing from the docker registry.
My latest version remains 2.19.4  :-(
Thanks

@jamescarppe I tried pulling the portainer/portainer-ce latest image but I get nothing from the docker registry. My latest version remains 2.19.4 :-( Thanks

You will need to use the version-specific :2.20.1 tag or the :sts meta tag, as the 2.20 branch is a STS (Short-Term Support) release and as such is not referenced by the :latest tag. You can find more information about what this means in our 2.20 release blog post .

I did so and got it updated. However, still can't connect to the console. Inspect, however, now works again.

Thanks - we're downgrading I believe temporarily until this is resolved.

I did so and got it updated. However, still can't connect to the console. Inspect, however, now works again.

I personally confirmed console access was fixed so you should be good to go. Try clearing your browser cache, or perhaps the image your container uses doesn't support consoling in.

Confirmed fixed on our QA Docker v26 Swarm including executing a console.
The only issue I can see is when consoling onto a Windows node with PowerShell I see this appear on login

clear
export LC_ALL=C.UTF-8
export LANG=C.UTF-8

I saw this on 2 different images and don't recall seeing it in the past. However it seems to have no adverse affects if you press ctrl+c or enter and then have a working shell. It might be something our side so will look into that but we hardly have any Windows services anyway so no big deal. Well done everyone involved with the fix.

@jamescarppe
There is a bug in version 20.01 of portainer. An image is marked as "unused" when the container has been "exited" :-(
Thanks

Same issue . For me, its works. Ubuntu version: ubuntu.20.04~focal
sudo apt install docker-ce=5:25.0.5-1~ubuntu.20.04~focal

@jeremyjohn
Portainer has been updated no need to downgrade anymore just pull and update portainer

@Paillat-dev
The 20.01 from sts tag is affected by a bug that I reported in this issue
https://github.com/portainer/portainer/issues/11511
Thanks

@Error00101 @jamescarppe
The sts includes many bugs, I'm sticking with my old version until the new lts
https://github.com/portainer/portainer/issues/11511

Yeah I know there are bugs maybe I should have mentioned it, I mean it depens on if it affects you or not

Downgrading the docker version worked for now
Ubuntu 22.04:
VERSION_STRING=5:25.0.5-1~ubuntu.22.04~jammy
sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

Upgrading Portainer to image portainer/portainer-ce:sts  works on Raspberry Pi 5 arm64 Debian Bookworm. Thank you devs.

I did so and got it updated. However, still can't connect to the console. Inspect, however, now works again.

I personally confirmed console access was fixed so you should be good to go. Try clearing your browser cache, or perhaps the image your container uses doesn't support consoling in.

Well, I tried it on different clients with multiple containers that always worked before (e.g. nginx web server). It says "Exec into container as default user using command bash Connecting..." and that's it. Any ideas?

I did so and got it updated. However, still can't connect to the console. Inspect, however, now works again.

I personally confirmed console access was fixed so you should be good to go. Try clearing your browser cache, or perhaps the image your container uses doesn't support consoling in.

Well, I tried it on different clients with multiple containers that always worked before (e.g. nginx web server). It says "Exec into container as default user using command bash Connecting..." and that's it. Any ideas?

did you try with ash and or sh?
Any errors in your browser's developer console (ctrl+maj+I)?

This is another repeated cycle of unintentional Docker updates with OS updates. #10983
I would recommend :

for those like myself who don't know, for ubuntu and debian style systems this will allow all other upgrades to happen except the docker upgrade
apt-mark hold docker-ce*

to cancel the hold:
apt-mark unhold docker-ce*
until Portainer predicts what's docker is up to next.
https://www.portainer.io/blog/portainer-and-docker-26

I did so and got it updated. However, still can't connect to the console. Inspect, however, now works again.

I personally confirmed console access was fixed so you should be good to go. Try clearing your browser cache, or perhaps the image your container uses doesn't support consoling in.

Well, I tried it on different clients with multiple containers that always worked before (e.g. nginx web server). It says "Exec into container as default user using command bash Connecting..." and that's it. Any ideas?

did you try with ash and or sh?
Any errors in your browser's developer console (ctrl+maj+I)?

Yes, tried all shells. None worked.
In the log there is the following error:
"containerConsoleController.js:181 WebSocket connection to 'wss:///api/websocket/exec?endpointId=2&id=8e2ae6040e58b4d860551caf1880a65c37afee49d0b50a466b3716e80e79e9fe' failed"
Also, two regarding German translations missing.

In the log there is the following error: "containerConsoleController.js:181 WebSocket connection to 'wss:///api/websocket/exec?endpointId=2&id=8e2ae6040e58b4d860551caf1880a65c37afee49d0b50a466b3716e80e79e9fe' failed"
@Mittlebenskrise
That's what I was thinking.  I know in some cases you might have disabled websockets in them, you need to make sure they're enabled

Here as well.
Docker version 26.0.0, build 2ae903e
portainer/portainer-ce:2.19.4

In the log there is the following error: "containerConsoleController.js:181 WebSocket connection to 'wss:///api/websocket/exec?endpointId=2&id=8e2ae6040e58b4d860551caf1880a65c37afee49d0b50a466b3716e80e79e9fe' failed"

@Mittlebenskrise That's what I was thinking.  I know in some cases you might have disabled websockets in them, you need to make sure they're enabled

Thanks for this hint! Just adding these two lines to my nginx configuration solved the issue for me (might be helpful for others as well):
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";

As the problem referred to in this issue has been resolved with the release of 2.20.1, I am closing the issue. Other problems should be raised in separate tickets where appropriate.

Still had that issue on portainer 2.20.1 with docker 26.0.0
Updating docker to 26.0.1 fixed that issue.

Upgrading Portainer to image portainer/portainer-ce:sts

This also works if you're running Ubuntu 22.04.4 LTS.

It work after i upgrading to portainer/portainer-ce:sts verison.
Just follow this documentation:
https://docs.portainer.io/v/2.20/start/upgrade/docker

As the problem referred to in this issue has been resolved with the release of 2.20.1, I am closing the issue. Other problems should be raised in separate tickets where appropriate.

I'm running portainer on windows with the following versions:
portainer version: portainer/portainer-ee:windowsltsc2022-amd64-2.20.1
docker version: 26.0.1, build d260a54
Unfortunately the problem still persists, at least for in a Windows environment.

:latest was stuck on 2.19.4 for me, changing to 2.20.1 definitely fixed. Preciate it. Didn't quite catch the BOLD text saying it was outdated lol

Previously downgraded Docker to 25.0.5 to make it work with Portainer. Somehow Docker got updated to 26.0.1 at some point, and ran into the issue again with portainer-ce:latest. Restarted with portainer-ce:sts which pulled 2.20.1, but it did not work.
Updating Docker to 26.0.2 solved it.

@jamescarppe
I tried again, but unfortunately with the following new version of Docker 26.0.2, the problem remains. Also, is still present the dangerous bug , that an image with container "stopped" state is shown as "unused"
Client: Docker Engine - Community
 Version:           26.0.2
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        3c863ff
 Built:             Thu Apr 18 16:27:45 2024
 OS/Arch:           linux/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          26.0.2
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       7cef0d9
  Built:            Thu Apr 18 16:27:45 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

We are very far from a definitive solution, I hope it won't be long until the next LTS. In the meantime I was forced downgrade  to Docker 25.0.5  and the latest LTS of Portainer 2.19.4

We have seen some users still experiencing the issue after updating to 2.20.1 that have resolved the issue through clearing their browser cache and/or doing a force refresh of the page. Those that are still seeing it, are you able to try this (or try in a different browser)?

A force refresh using Ctrl + R worked for me

I have portainer 2.20.1 and Docker 26.1.0, until further notice it runs ok.

God bless this fix

VERSION_STRING=5:25.0.5-1~ubuntu.20.04~focal
sudo apt-get install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin

it  work   ，thx

We have seen some users still experiencing the issue after updating to 2.20.1 that have resolved the issue through clearing their browser cache and/or doing a force refresh of the page. Those that are still seeing it, are you able to try this (or try in a different browser)?

what about business edition? it says 2.19.5 is the latest version and I'm still having this issue.
thanks

@mamama1 For business you need to switch to Short-Term Support (STS) branch. - https://www.portainer.io/blog/portainer-2.20-release
Switch to portainer/portainer-ee:sts from latest in your docker compose or pull

Thanks! I actually already downgraded Docker CE which solved the issue as well and did apt-mark hold docker-ce*. Since this is now working, I think I'll stick to the old Docker version, until Portainer Business LTS supports the new Docker version.
Is there an estimate on when this will be true?

Upgrading Portainer to image portainer/portainer-ce:sts works on Raspberry Pi 5 arm64 Debian Bookworm. Thank you devs.

Thanks! this fixed it for me:
im running: Red Hat Enterprise Linux 9.4

Raspberry PI 4 8Gig - Bookworm Server 64Bit
Docker version 26.1.2, build 211e74b
portainer/portainer-ce:latest
Removed and pulled latest Portainer image
Cleared cache
Tried different browser
err:
Failure
Unable to retrieve image details

@prichardsondev
Unfortunately, the fix is only available at the Short Term Support (STS) branch. Officially supported Docker versions are 23.0.6 through 24.0.4. Try the following image.
portainer/portainer-ce:sts

Deploying with: portainer/portainer-ce:sts you will get Portainer CE 2.20.2
Issue "unable to exec console" it is solved.
It should be great to have a LTS version with that patch.

Deployed portainer/portainer-ce:sts on Raspberry Pi4 8GB and worked like a glove.
Just clear the browser cache or use a diff browser to validate.

I encountered the same problem as everyone else. Instead of downgrading Docker, I simply updated to Portainer 2.20.1. Interestingly, this version doesn’t come with a ‘latest’ tag (where ‘latest’ today corresponds to v19).
Attention: Despite the update, the error persisted. However, with version v20, I used CTRL+R in the container window, and everything worked perfectly.
I removed the old container (using docker stop and docker rm) and installed the new one:
docker run -d -p 9000:9000 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.1

Working perfectly:

System:  Ubuntu 22.04.4 LTS -  jammy
Docker: v26.1.3
Portainer: /portainer-ce:2.20.1

Still having this problem on portainer/portainer-ee:2.20.2 with docker v26.1.3

Change the browser.
On Sat, May 18, 2024, 1:33 p.m. mauvehed @.***> wrote:

Still having this problem on portainer/portainer-ee:2.20.2 with docker
v26.1.3
—
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/11436#issuecomment-2118984654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKNVHBNYCJM6MOMQMDEAUF3ZC6UIFAVCNFSM6AAAAABFAOCPXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYHE4DINRVGQ
.
You are receiving this because you commented.Message ID:
@.***>

I encountered the same problem as everyone else. Instead of downgrading Docker, I simply updated to Portainer 2.20.1. Interestingly, this version doesn’t come with a ‘latest’ tag (where ‘latest’ today corresponds to v19).
Attention: Despite the update, the error persisted. However, with version v20, I used CTRL+R in the container window, and everything worked perfectly.
I removed the old container (using docker stop and docker rm) and installed the new one:
docker run -d -p 9000:9000 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.1

Working perfectly:

System:  Ubuntu 22.04.4 LTS -  jammy
Docker: v26.1.3
Portainer: /portainer-ce:2.20.1

This worked perfectly for me

@jeremydthomas any reasons why the latest is old? :D

@jeremydthomas any reasons why the latest is old? :D

As per this comment:

@jamescarppe I tried pulling the portainer/portainer-ce latest image but I get nothing from the docker registry. My latest version remains 2.19.4 :-( Thanks

You will need to use the version-specific :2.20.1 tag or the :sts meta tag, as the 2.20 branch is a STS (Short-Term Support) release and as such is not referenced by the :latest tag. You can find more information about what this means in our 2.20 release blog post .

I updated Portainer and it fixed it for me as well. Now running portainer/portainer-ce:2.20.3-alpine

@jamescarppe
It's very frustrating to follow this conversation. We are waiting for a new stable version of Portainer but we still don't know when it will be released. In addition to the one discussed there are many bugs that the sts version has not yet solved, such as this annoying bug
https://github.com/portainer/portainer/issues/11511
Do you have any news on when the stable version will be released?
Thank you

Based on the feedback from multiple people here, I think the easiest temporary fix is to rename the latest tag to match v2.20.1 which addresses the problem. You can do so, using:
# Portainer fix - use v2.20.1. instead of 2.19 so that it works with the latest docker API
sudo docker image rm portainer/portainer-ce:latest
sudo docker pull portainer/portainer-ce:2.20.1
sudo docker image tag portainer/portainer-ce:2.20.1 portainer/portainer-ce:latest

Then you can run your regular portainer setup commands.

@GramThanos
Is there a reason why I need to rename (tag) version 2.20.1 with the latest tag?
The version 2.20.1 also does not fix the following bug
https://github.com/portainer/portainer/issues/11511

@jamescarppe It's very frustrating to follow this conversation. We are waiting for a new stable version of Portainer but we still don't know when it will be released.

As mentioned in the Portainer and Docker 26 blog post that has been linked many times in this thread, 2.21 will be our first LTS release and at this point is due in the next month or so. I don't have an exact date to share at this stage as there is a substantial amount of testing required to ensure 2.21 is as stable as it can be.

In addition to the one discussed there are many bugs that the sts version has not yet solved, such as this annoying bug
#11511

Any information regarding other already-raised bugs will be provided in the issues for those bugs. I would recommend checking there rather than re-raising it multiple times in unrelated issue threads.

I encountered the same problem as everyone else. Instead of downgrading Docker, I simply updated to Portainer 2.20.1. Interestingly, this version doesn’t come with a ‘latest’ tag (where ‘latest’ today corresponds to v19).
Attention: Despite the update, the error persisted. However, with version v20, I used CTRL+R in the container window, and everything worked perfectly.
I removed the old container (using docker stop and docker rm) and installed the new one:
docker run -d -p 9000:9000 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.1

Working perfectly:
* System:  Ubuntu 22.04.4 LTS -  jammy

* Docker: v26.1.3

* Portainer: /portainer-ce:2.20.1

Thanks a lot man for the command !
Before i was able to use i did a force remove first !
docker rm portainer -f

Glad to see that I am not the only one with this issue.  I tried upgrading my Portainer to:
Standalone 26.1.3 and I still get that error.
Docker version 26.1.3, build b72abbb

Same issue here...
Docker Engine 26.1.4
Portainer Community Edition 2.19.1
Fedora 40
I'm not downgrading and hope this issue will get resolved as quickly as possible.

I encountered the same problem as everyone else. Instead of downgrading Docker, I simply updated to Portainer 2.20.1. Interestingly, this version doesn’t come with a ‘latest’ tag (where ‘latest’ today corresponds to v19).
Attention: Despite the update, the error persisted. However, with version v20, I used CTRL+R in the container window, and everything worked perfectly.
I removed the old container (using docker stop and docker rm) and installed the new one:
docker run -d -p 9000:9000 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.20.1

Working perfectly:
* System:  Ubuntu 22.04.4 LTS -  jammy

* Docker: v26.1.3

* Portainer: /portainer-ce:2.20.1

Thanks a lot man for the command !
Before i was able to use i did a force remove first !
docker rm portainer -f

Solved my problem too, thanks!

portainer/portainer-ce:2.20.1

Thanks worked for me too!

portainer/portainer-ce:2.20.1

Thanks worked for me too!

For me - only using 2.20.3 helped to get the console working again.

Is there a reason why 2.20.3 isnt "latest"? when will the latest tag be updated?

Is there a reason why 2.20.3 isnt "latest"? when will the latest tag be updated?

Long-Term Support releases, on the other hand, will not contain new features and will be focused on stability. We'll be taking what we added in the previous STS release, comprehensively testing for issues and regressions, and supplying what we consider production-ready LTS images. The LTS images will be our recommended images, and version 2.21 is planned to be our first LTS release.
As part of this we're also changing the way we tag our images. The :latest tag will now only be updated with LTS releases instead of every release. Since 2.20 is a STS release, the :latest tag will remain pointing to 2.19.5.

https://www.portainer.io/blog/portainer-2.20-release

so LTS users are being punished by not getting patches or what? since when LTS can't get bugfixes, until the next LTS release has been released?
isn't this all just about getting a bug fixed in LTS?

The current fix for this issue is not full Docker 26 support - that will come with our first LTS release, 2.21. Our LTS releases are intended to be as stable as possible for our users, but we wanted to get this "workaround" out for users that are on Docker 26 in the meantime.

@jamescarppe
Is there a roadmap for the release of the LTS 2.21 version?
Thanks in advance

I updated to 2.20.3, it says I'm running "Portainer Business Edition 2.20.3" at the bottom of the page, and yet I can now not only not view image details, but if I try to remove an old image, I get "Forbidden - CSRF token not found in request"

Oh, never mind that. I should probably have closed the browser tab, or even the full browser, first...

@jamescarppe Is there a roadmap for the release of the LTS 2.21 version? Thanks in advance

We're currently in code freeze for 2.21 with testing underway. I don't have an exact release date for you but we're targeting July at this stage.

I would like to know if docker v 27.0.1 which is out now has the same issues with CE ver 2.19.x ?

I would like to know if docker v 27.0.1 which is out now has the same issues with CE ver 2.19.x ?

The issue in 2.19 is due to a return value that was removed in Docker 26, so yes, Docker 27 will have the same issue.

portainer/portainer-ce:2.20.1

Use this version fixed this console issue for me too
Many thanks

@jamescarppe  Still getting the same issue with Portainer v2.20.3 and Docker 27.0.2, I hope this will be sorted out in the upcoming v2.21

@jamescarppe Still getting the same issue with Portainer v2.20.3 and Docker 27.0.2, I hope this will be sorted out in the upcoming v2.21

As mentioned in this thread already, clear your browser cache fully and this should resolve.

I'm using :latest with Docker 27.0.3 (3 new servers setup in the last week). It is clearly still not working for me.

@SponsorAds don't use latest, use 2.20.3 as described here

@avatar7008 same problem for me. I cleared cache and tried it on a brand new laptop where the site was never open. Problem still persists.
`Client: Docker Engine - Community
Version:           27.0.3
API version:       1.46
Go version:        go1.21.11
Git commit:        7d4bcd8
Built:             Sat Jun 29 00:02:50 2024
OS/Arch:           linux/amd64
Context:           default
Server: Docker Engine - Community
Engine:
Version:          27.0.3
API version:      1.46 (minimum version 1.24)
Go version:       go1.21.11
Git commit:       662f78c
Built:            Sat Jun 29 00:02:50 2024
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.7.19
GitCommit:        2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc:
Version:          1.7.19
GitCommit:        v1.1.13-0-g58aa920
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
`
Portainer has version 2.20.3.

just to make it clear for everyone (including myself):

latest is pointing to lts (currently 2.19.5), alternative is sts tag (currently 2.20.3)
error unable to retrieve image details is due to the fact that docker v27.y.z removed some capabilities; so whichever portainer version we use, the only way to see image details at this moment is to go back to docker v26.y.z

correct @jamescarppe (especially 2nd point) ?

just to make it clear for everyone (including myself):

latest is pointing to lts (currently 2.19.5), alternative is sts tag (currently 2.20.3)
error unable to retrieve image details is due to the fact that docker v27.y.z removed some capabilities; so whichever portainer version we use, the only way to see image details at this moment is to go back to docker v26.y.z

correct @jamescarppe (especially 2nd point) ?

No point two is wrong as detailed by the edit "EDIT FOR TLDR (April 5, 2024)" at the start of this ticket description. If you run the STS or 2.20.3 version the issue is fixed. I can confirm at my workplace, we've been using the 2.20 versions successfully with Docker 26 since this issue was fixed in 2.20.1. Several users have reported having to clear caches and close browsers before it worked after upgrading Portainer.
I strongly suspect the biggest cause of confusion has been latest tag pointing at the latest LTS version and not just the latest version across all released versions. This is deliberate and mentioned on https://www.portainer.io/blog/2024-release-principle
Additonally for some reason the LTS version never got fixed for this issue despite it being months, contrary to assumptions about what LTS might mean for some major breakage like this.
The bottom line is right now you can use the STS version and it will work and we should have a new fixed LTS version in the coming weeks.

Like @felipewnp, I still have this issue with the latest Portainer release. I have created a stack from Docker Hub (Nginx Proxy Manager), and whether I click Console or Attach in the Stack/Container, I get the same error mentioned in this issue. This issue affects all Stacks & Containers I currently have running, no matter how they were added to my Portainer instance.

@jmessy919
You must use the Docker 2.20.3 or sts tag. I'm observing that you are still using version 2.19.5
You also need to make sure you clear your browser cache
Thanks

Thanks @corasaniti - didn't know it wasn't yet pushed to the latest tag. I learned something new, and after applying the sts tag instead, everything works as intended. Cheers.

Thank you @corasaniti. sts tag worked like a charm.
Also, I want to ask for a favor to Portanier team. Can you guys please update YML files referenced inside the official guideline "Install Portainer CE with Docker on Linux"?
This will save others' time. Thanks

Also, I want to ask for a favor to Portanier team. Can you guys please update YML files referenced inside the official guideline "Install Portainer CE with Docker on Linux"?

The documentation you have linked is for 2.19. For 2.20 documentation, you can use the version dropdown at the top of the documentation page to select the 2.20 documentation, or go to https://docs.portainer.io/v/2.20.
The default documentation version displayed corresponds to the most recent non-STS version, which at present is 2.19. When 2.21 LTS is released, the default documentation will be updated to point to that version's documentation.

@jamescarppe could you please address my question here please?
that still doesn't work on the latest sts

error unable to retrieve image details is due to the fact that docker v27.y.z removed some capabilities; so whichever portainer version we use, the only way to see image details at this moment is to go back to docker v26.y.z

I am running Portainer 2.20.3 on Docker 27.0.3 and do not have this issue. The change that caused this was in Docker 26, and the fix applies to versions 26 and above, including 27. Make sure you clear your browser cache / local storage, and/or try from another browser or incognito.

@jamescarppe
Hello james
I'm also experiencing this issue after upgrading Docker to version 27.1.0.
Due to the security vulnerability CVE-2024-41110, I was forced to upgrade to version 27.1.0. Currently, I'm having trouble accessing the console and images through Portainer.
Portainer version
2.16.2
Portainer Edition
Business Edition (BE)
Docker version:
27.1.0

As has already been mentioned in this thread, and is displayed at the top of the original issue:

Portainer 2.20.3 has now been released, which includes a fix for these issues under Docker 26 and above. We recommend updating to 2.20.3 if you need to use Docker 26 or above.

Update to 2.20.3 and clear your browser cache.

No meu caso tenho o docker 27.
Actualizei o portainer para a 2.20.3
Limpei o cache do navegador.
E voltou a funcionar perfeitamente

As has already been mentioned in this thread, and is displayed at the top of the original issue:

Portainer 2.20.3 has now been released, which includes a fix for these issues under Docker 26 and above. We recommend updating to 2.20.3 if you need to use Docker 26 or above.

Update to 2.20.3 and clear your browser cache.

Any plans on incorporating the fix on portainer-ce ?

Any plans on incorporating the fix on portainer-ce ?

The fix is there for both CE and BE on the 2.20 version. For CE, that would be portainer/portainer-ce:2.20.3.

Any plans on incorporating the fix on portainer-ce ?

The fix is there for both CE and BE on the 2.20 version. For CE, that would be portainer/portainer-ce:2.20.3.

I've used portainer/portainer-ce:latest which seems the tag is not pointing to latest version.

I've used portainer/portainer-ce:latest which seems the tag is not pointing to latest version.
Which is instructed here: https://docs.portainer.io/start/install-ce/server/docker/linux

Don't use portainer/portainer-ce:latest if you need Docker 26+ support. Use portainer/portainer-ce:2.20.3. As already covered here, the 2.20 branch is not a LTS release and thus won't be tagged with latest. 2.21 will be the first LTS with Docker 26+ support and will be tagged latest when it is released.
https://www.portainer.io/blog/2024-release-principle

I've used portainer/portainer-ce:latest which seems the tag is not pointing to latest version.
Which is instructed here: https://docs.portainer.io/start/install-ce/server/docker/linux

Don't use portainer/portainer-ce:latest if you need Docker 26+ support. Use portainer/portainer-ce:2.20.3. As already covered here, the 2.20 branch is not a LTS release and thus won't be tagged with latest. 2.21 will be the first LTS with Docker 26+ support and will be tagged latest when it is released.
https://www.portainer.io/blog/2024-release-principle

Will follow, but be aware:  the term LTS nor a short "FYI" about pulling latest not being latest in the "start install" guides.
IMHO this should be mentioned as 99% of users will follow the "start install" guides when installing portainer and will never know about the 2024 release principle.

I've used portainer/portainer-ce:latest which seems the tag is not pointing to latest version.

Which is instructed here: https://docs.portainer.io/start/install-ce/server/docker/linux

Don't use portainer/portainer-ce:latest if you need Docker 26+ support. Use portainer/portainer-ce:2.20.3. As already covered here, the 2.20 branch is not a LTS release and thus won't be tagged with latest. 2.21 will be the first LTS with Docker 26+ support and will be tagged latest when it is released.
https://www.portainer.io/blog/2024-release-principle

Instead of latest, use sts tag. Worked out for me

Will follow, but be aware: the term LTS nor a short "FYI" about pulling latest not being latest in the "start install" guides.
IMHO this should be mentioned as 99% of users will follow the "start install" guides when installing portainer and will never know about the 2024 release principle.

The current base documentation is for 2.19 so is written around that. As 2.20 is a STS release it isn't the default documentation version displayed, but you can select 2.20-specific docs with the version dropdown at the top of the documentation.
Once 2.21 is released that will become the default documentation and this won't be an issue.

Will follow, but be aware: the term LTS nor a short "FYI" about pulling latest not being latest in the "start install" guides.
IMHO this should be mentioned as 99% of users will follow the "start install" guides when installing portainer and will never know about the 2024 release principle.

The current base documentation is for 2.19 so is written around that. As 2.20 is a STS release it isn't the default documentation version displayed, but you can select 2.20-specific docs with the version dropdown at the top of the documentation.
Once 2.21 is released that will become the default documentation and this won't be an issue.

Again, I didn't select any version.
I could, if I knew latest is not really latest... (which now I know latest is actually latest-lts)
I used the URL (which most users will get from google) which is https://docs.portainer.io/start/install-ce/server/docker/linux
All I suggest is to give an indication this version is not compatible with the latest Docker and is not really latest and the user should check the 2.20 page or use sts (which worked in my case)

Again, I didn't select any version. I could, if I knew latest is not really latest... (which now I know latest is actually latest-lts)

This is primarily due to historical reasons - we started the STS/LTS process with 2.20, and we were already where we were with 2.19 before that, and then the Docker 26+ issue appeared. This will be resolved with the 2.21 issue, which should only be a few weeks away.

I used the URL (which most users will get from google) which is https://docs.portainer.io/start/install-ce/server/docker/linux
All I suggest is to give an indication this version is not compatible with the latest Docker and is not really latest and the user should check the 2.20 page or use sts (which worked in my case)
I fail to see the problem adding this to the landing page which most users will land on.

I've added warning boxes to the Docker installation pages in docs now. Hopefully this should help.

any update on this?  I'm on v2.16.2 and still seeing this issue

@poldim
2.21.4 has been released for at least 2 months...

@poldim 2.21.4 has been released for at least 2 months...

Just figured out my backup site was still running on portainer:latest.  For anyone else, make sure you have ce version

@poldim 2.21.4 has been released for at least 2 months...

Just figured out my backup site was still running on portainer:latest. For anyone else, make sure you have ce version

'portainer-ce:sts' for long term support. I think the term latest was dropped a month ago.

'portainer-ce:sts' for long term support. I think the term latest was dropped a month ago.

STS stands for Short-Term Support, whereas LTS is for Long-Term Support. The latest tag points to the most recent LTS build. We cover this in depth in our lifecycle policy document.


Fix deprecation for Symfony 6.3

Thank you!

Hi, may I ask for a patch release including this PR? Thanks! :)

v1.8.3 is out, sorry for the delay 👍


Not working

react-native-rename NewName
The app_name value in ./android/app/src/main/res/values/strings.xml must be the same with ./ios/AppFolderName before renaming the app.
ex. ./ios/CoolApp  --->  <string name="app_name">CoolApp</string>

I am getting this error but this name is the same before I run the command.

I am using rn 0.40

react-native-rename "Master"
/home/user-pc/.nvm/versions/node/v5.0.0/lib/node_modules/react-native-rename/lib/index.js:169
} else if (err.code === 'ENOENT') {
^
TypeError: Cannot read property 'code' of undefined
at /home/user-pc/.nvm/versions/node/v5.0.0/lib/node_modules/react-native-rename/lib/index.js:169:16
at tryToString (fs.js:414:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:401:12)

I confirm. I have this problem too.

Same problem here

I just tested it using react-native 0.43.3 and it works.

Worked for me with react-native 0.44.0


Unable to get property 'compilerOptions' of undefined or null reference - with valid tsconfig.json after 1.8 upgrade rolled back

I've been experimenting with 1.8 upgrade. I've put this on a branch for our repository and checked out master. Unfortunately, the master branch no longer builds.
1>VSTSC : tsc.js(31087, 13) JavaScript runtime error : Unable to get property 'compilerOptions' of undefined or null reference
I've checked this error and it seems to be a bug in TS 1.7 when tsconfig.json is invalid JSON. Unfortunately, my tsconfig.json is very much valid JSON. I checked an online JSON validator, which gives it the green light, as does VS's intellisense and also the fact that the master branch built just fine before trying 1.8.
Here's the entirety of our tsconfig.json:

{
  "compilerOptions": {
    "sourceMap": true,
    "outDir": "bin-js",
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "experimentalDecorators": true
  },
  "files": [
    "../Dependencies/require.d.ts",
    "../Dependencies/d3.d.ts",
    "../Dependencies/d3.element.d.ts",
    "../Dependencies/d3.event.d.ts",
    "../Dependencies/history.d.ts",
    "../Dependencies/jquery.d.ts",
    "../Dependencies/jquery.promise.d.ts",
    "../Dependencies/jquery.when.d.ts",
    "../Dependencies/jquery.cookie.d.ts",
    "../Dependencies/jquery.autosize.d.ts",
    "../Dependencies/moment.d.ts",
    "../Dependencies/moment-fixes.d.ts",
    "../Dependencies/rangy-core.d.ts",
    "../Dependencies/route-recognizer.d.ts",
    "../Dependencies/underscore.d.ts",
    "../Dependencies/jasmine.d.ts",
    "../Dependencies/jasmineAddons.d.ts",
    "../Framework/InterfaceExtensions.ts"
  ]

}

If I delete the files, the build passes, so they're clearly involved, but not only are they clearly valid JSON, but TS 1.7 accepted them quite happily prior to me trying out the 1.8 update.

@markboyall the tsconfig.json seems fine. the problem seems to be somewhere else. can you share a sample project that we can look at. feel free to email me directly at mhegazy at microsoft dot com

I'll try to create a reproduction locally today.

Same thing happening with me after upgrading to version TypeScript Tools 1.8.6, project was compiling fine before.

@tritao can you share more details.

@mhegazy
I have a pretty simple project with this config file:
{
    "compilerOptions": {
        "target": "es6",
        "module": "es6",
        "sourceMap": true,
        "jsx": "react"
    },
    "exclude": [
        "node_modules",
        "typings/main.d.ts",
        "typings/main"
    ],
    "files": [
        "app/index.ts",
        "app/components/App.tsx",
        "app/components/Item.tsx",
        "app/components/ItemList.tsx",
        "typings/browser.d.ts"
    ]
}

and get this error when I try compiling:
VSTSC(0,0): error : Unable to get property 'compilerOptions' of undefined or null reference

How can I help further narrow down the issue?

in your project file what is the "TypeScriptToolsVersion" property set to?

you will need to right-click unload project, then edit the file.

Looks like I had not properly installed the TypeScript VS 2015 plugin, now VS reports the correct version and the project is building again, sorry for the noise.

Just a note, the build will always use TypeScriptToolsVersion value if specified. if you do not care to keep the compiler "frozen" at a specific version, you can remove the value all together, and that means it will always be using the latest installed.

@mhegazy
I am running into the same issue. I have the 1.8 tools installed. I have tried updating the "TypeScriptToolsVersion" in my project file to 1.8 and removing the value. The error still does not go away. Any thoughts?

@brianj1084 can you share the build log?

@mhegazy I figured it out. We had a 'TscToolPath' property set in our csproj that was pointing to the 1.7 tools. I removed that property and everything worked.

Thanks for following up! Glad it got fixed

I am using VS 2015 Update 3 and TS (1.8.35). I tried everything mentioned in previous comments but still facing same issue.
Unable to get property 'compilerOptions' of undefined or null reference
Contents of my tsconfig.json:
{
  "compileOnSave": true,
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "noImplicitAny": false
  },
  "exclude": [
    "node_modules",
    "typings/main",
    "typings/main.d.ts",
    "Scripts/TypeLite.Net4.d.ts"
  ]
}

I caught the issue in my case and found the solution. I was installing latest version of TS (1.8.6) but studio was still showing me TS (1.8.35) in Help > About Microsoft Visual Studio. The issue was related to VS component cache. I installed an extension (https://visualstudiogallery.msdn.microsoft.com/22b94661-70c7-4a93-9ca3-8b6dd45f47cd) to manually clear and rebuild component cache. After clearing the cache, I just loaded the project and it got compiled.


publish<EMAIL_ADDRESS>

Requested by: @stayallive
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] github
[ ] registry

The tag was made so I think it did work and that is why the branch is gone?
https://github.com/getsentry/sentry-laravel/releases/tag/2.6.0
I did not delete it myself or anything!?

Ah, interesting. Looks like it worked but got stuck or something 😅


Drag external element into tree

Hi Team,
Please provide an example as to how to drag an external element into the tree.
The documentation only states to provide a custom handler, but do i need to create a new TreeNode from the external element? If this has been answered at some point, with an example or some further guidance, please do let me know,

how to determine if the nodes is coming in external tree?

@musti2 Hi where you able to find out how to do it?
BR

I suggest to create a function createNode that can be used in the mapping drop callback to ease the job of node creation. By looking at the implementation of moveNode I was able to create the node like this
actionMapping: {
  mouse: {
    drop: (tree, node, $event, {from, to}) => {
      // tree.createNode(from, to);  in the futur?
      if (!to.parent.getField('children')) {
        to.parent.setField('children', []);
      }
      const toChildren = to.parent.getField('children');

      // here my from is {
      //   id: 8,
      //   name: 'Parent 8'
      // }
      // so it does have an id but you can use your getNodeClone to generate a
      // new node with a unique ID
      toChildren.splice(to.index, 0, from);

      tree.update()
    }
  }
}


⚠ Bofrost.fr has degraded performance

In f4c2402, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 937 ms

Resolved: Bofrost.fr performance has improved in 727401c after 6 minutes.


Add Gogs

Would like to add Gogs for private Git source control

Gitea appears to be the better of the two projects.

You've hit the exact reason I hadn't progressed with this yet :-)
My ideas were either;

Document assigning an additional IP to the Ubuntu box, then have a config item of something like gitea_ip_to_use = <IP_ADDRESS>. https://www.garron.me/en/linux/add-secondary-ip-linux.html. I think this would require some extra retro-fitting to tell various services to use the first configured IP.

The same as your 2.

Thoughts?

That's certainly a possibility, but is it a bit of overkill for what will generally be a home NAS? Then again, changing the host SSH port falls in to that category as well...
So we have:

Add multihomed functionality to our host
Move host SSH to a new port (my preference, just as a good security practice, even though it is just a home NAS)
Move Gitea to a different SSH port
Disable SSH access to Gitea, and document that people can only use HTTP(S) for interacting (not a terrible option. Bad, but not terrible)

Say we went with host SSH change. Realistically, how many people are likely to enable gitea? If we document it such that this is an "advanced option", it might be ok. We'd certainly have to ensure that people don't run the playbook on the localhost (restarting SSH). Or that if enabling gitea, you must run playbook A, reconnect to new port, run playbook B (ugly).
I'll have a crack at my preferred option and see how it pans out. I'll raise a PR once I've got what I'd call a working version.
Regards,
CJ

My preference is that we leave SSH on the normal port, and Gitea gets a non-standard port.
Having SSH on a different port would be annoying every time you try to connect to your NAS, whereas Gitea on a different port is likely to not be noticed, given any clone of a repo is a cut and paste of the URL the application gives you...

You have a good point. Also the gitea documentation suggests that moving gitea to a different port is a common practice (https://docs.gitea.io/en-us/install-with-docker/ )
I've got it running, just tweaking some of the options that are available via ENV settings for a cleaner install experience. Have a look if you like before I raise a PR for it.
I'd be interested in knowing how to get Ansible to inject the FQDN of the host...


Implement

It would be useful to have a <Shown/> component that complements <Hidden/> by working in the exact opposite way based on the properties it receives. The <Grid/> component would also be extended to allow a shown property instead of hidden.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
The configuration to <Shown /> would use the same prop types and values as <Hidden /> but it would do the opposite thing, e.g. if mdUp is passed as a prop then it would render its children only if the window is medium-sized or larger.
Context
It is more intuitive (to me) in many scenarios to indicate when I want something shown, rather than when I want it hidden. For example, I may wish to render a single column of content in an xs window, 2 columns in sm, and 3 in md or larger. The syntax using the <Shown/> component would then look like this:
<Shown only='xs'>
  <Column />
</Shown>

<Shown only='sm'>
  <Column />
  <Column />
</Shown>

<Shown mdUp>
  <Column />
  <Column />
  <Column />
</Shown>

By comparison, the <Hidden/> component would have to be set up like this:
<Hidden smUp>
  <Column />
</Hidden>

<Hidden mdUp xsDown>
  <Column />
  <Column />
</Hidden>

<Hidden smDown>
  <Column />
  <Column />
  <Column />
</Hidden>

It's more difficult to understand the logic / intent in the <Hidden/> example.

It would be useful to have a  component that complements  by working in the exact opposite way based on the properties it receives. The  component would also be extended to allow a shown property instead of hidden.

@idrm Going forward, we plan on removing the hidden property from the Grid. It's an API sugar that I don't think provide much. Regarding your Show / Hide concern. I agree, we plan on working on a Display component to address the need and more: #10828.

@oliviertassinari fwiw we see that Display can now do this, but FWIW given that Hidden is already / will always be in the public API, we think it'd still be nice to have the complement, Shown, available, for consistency.


NFT card preview

Hello @SR-Sunny-Raj , I want to add a simple html and css project , can you pls assign me this under hacktoberfest2022

Sorry to inform but this repository has been excluded from hacktoberfest. So inorder to make your PR count towards hacktoberfest, request you to make your contribution in this repository -> https://github.com/SR-Sunny-Raj/Hacktoberfest2022-for-all


Better handle Chrome extension errors on browser launch

Steps to reproduce
What steps will reproduce the problem?

Launch Chrome with an extension that doesn't exist or has some sort of error in its manifest

const puppeteer = require("puppeteer")
puppeteer.launch({
  args: ["--load-extension=/tmp/doesnt-exist"],
  ignoreDefaultArgs: ["--disable-extensions"],
  headless: false
}).then(() => { })

What happens?
There's an exception:

UnhandledPromiseRejectionWarning: TimeoutError: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r756035 is guaranteed to work.

Chrome displays an alert modal:

What is the expected result?
It would be nice if puppeteer crashed with a meaningful error message.
I run into this issue every now and then when running Puppeteer in Docker, so I don't know that there's an alert message. Chrome also doesn't print anything about the error to the console, so it's hard to identify the issue.
Is there something that can be done to handle this type of error better? Maybe there's some Chrome flag to make Chrome crash or log an actual error?

I'd like to set up an automated extension installation test, specifically so the build will fail when the extension is invalid (I keep getting UTF-8 errors on content scripts that slip past CI). While I could rely on timeouts before await browser.close(), an official error handling mechanism like what @mattzeunert suggested would be faster and more reliable.


Add env_run_lists attribute in role detail

Add env_run_lists in Role struct.

Fixes: https://github.com/go-chef/chef/issues/177
Signed-off-by: Vivek Singh<EMAIL_ADDRESS>

Thank you for the PR.

I'll get this merged.  It's the type of thing that's very hard to find so it's very much appreciated.
The merge will be next week or the week after.  I've got a rule for myself that changes have to actually work in tests against a real chef server (see examples and chefapi_test cookbook). We don't have any roles or environment tests created yet and setting that up takes most of a day for each type of entity.

Sure, thanks

@MarkGibbons Could you please let me know the steps that you follow for testing and development purposes?

I'll add some doc about testing and development.  I'll take the request as a really good suggestion.
Thanks
Basic ideas for adding an endpoint, assume you will repeat this process and each step multiple times:
Design the data structures for a new end point
Create go tests for each func.
Write the go code.
Add examples to exercise the functions in the chefapi_examples cookbook.

Create go code to call the functions. See the files in go-chef/chef/examples/cmd. Many times extra setup is required.
Create a shell script to call the go code.  See the files in go-chef/chef/examples/bin.
Write Inspec tests to verify the output.  Be aware that go map output does not alway have consistent ordering. The matching regex structures are rarely fun to write.
Commit the go-chef/chef (api client go code at least) changes to a branch and push to GitHub.   The chefapi.rb recipe would need to be updated to pull from the correct repo.
kitchen converge. - installs the code, spins up a chef server to test against
kitchen login - run the /bin commands and iterate on fixing the code. Both cmd code and chef client code. kitchen converge will install cmd and bin file changes without committing and pushing to GitHub. Changes to the chef api client code need to be committed, pushed and kitchen converge run again to get the changes installed.
While logged in to the virtual box image try adding "-tags" debug  the bin command.  Example
go run -tags debug ${BASE}/../cmd/client/clients.go ${CHEFUSER} ${KEYFILE} ${CHEFORGANIZATIONURL} ${SSLBYPASS} will produce output that shows the real request body returned from the chef server.  Note what you passed in and what you got back. Send updates for the documentation to https://github.com/chef/chef-web-docs
After things work ok. Create an inspec test for the endpoint that calls the bin command for the endpoint.  Run kitchen verify to run the full set of integration tests.

Run cookstyle -a in the go-chef/chef/examples/chefapi_examples directory
Run go fmt in the go-chef/chef directory
See if any documentation needs to be updated, check to see if any of the scattered TODOs are now now.
Commit and PR

This PR will be merged as part of #180


Running flye assemblies and getting error wanting contigs.paths file for spades

Hello,
I am running graphbin v 1.7.1 and python version 3.10.13
First, I was unable to get the python support scripts to work so I renamed all of my files to make naming consistent and made the csv file with custom scripts.
When I tried to run the following code:
graphbin --contigs /home/ejunkins/LS01_hifi_coveragebin/LS01_001_assembly_renamed_edges.fasta --binned /home/ejunkins/LS01_hifi_coveragebin/bins/001/contignames/edges/LS01_001_all_edges_graphbin.csv --graph /home/ejunkins/jgi_assemblygraphs/NGXTG/flye/assembly_graph.gfa --output /home/ejunkins/LS01_hifi_coveragebin/bins/001/graphbin_out --prefix graphbin_metabat2_LS01_001_bin_with_cov --assembler flye
I get this error:
2024-02-12 12:28:23,452 - ERROR - Please make sure to provide the path to the contigs.paths file. 2024-02-12 12:28:23,453 - INFO - Exiting GraphBin... Bye...!
My understanding was that this was only for spades assemblies...

Hello @emilyjunkins,
So sorry for getting back to you late.
GraphBin now supports the original contigs produced from Flye. The example command would look something like this.
graphbin --assembler flye --graph assembly_graph.gfa --contigs assembly.fasta --paths assembly_info.txt--binned binning_result.csv --output graphbin_out

The path option is required for both SPAdes and Flye assemblies as they produce a unitig graph instead of a contig graph.
Hope this clears things.

Closing this issue. Please re-open if needed.


Fixed html syntax for javaScript region start pattern

This fixes some weird syntax highlighting effects for markdown files.

Sorry. But it seems the correct pattern should be defined more precisely.
Now it does not match a simple case of  <script>
The idea is that if there is some text after the beginning of the tag -- <script, then it must necessarily begin with a space.


Alias apollo client in QueryManager

There are some instances where it makes sense to drop down to the Apollo client library when calling specialized functions. For exampleclient.reFetchObservableQueries()

Hi @venkatd, just want to see if you've tried adding a test for this. I'd like to get this PR merged but it needs some test coverage first.

Hi @bgentry sorry for the delay here I will add some test coverage to it this week!

Will be getting it to this week actually. Sorry for the delays!

@bgentry sorry for the massive delay on such a simple change. Let me know if this is what you had in mind. Not sure if we want this test be duplicated for ComponentQueryManager and RouteQueryManager but I figured if it works for the base mixin, the rest should be fine.

@venkatd yep, that looks great to me. I guess my only other concern (which I should have mentioned previously) is that the name generic name client stands some chance of conflicting with existing properties for current users. However, since this is a mixin, most cases I can think of would just override this (dependent on mixin order for multiple mixins).
So I think this is good to go. Thanks! 🎉✌

Great! That's a good point. Alternatively we could call the property apolloClient.

That’s probably a safer choice. If you want to PR that I’ll get it merged
right away :)
On Tue, Mar 27, 2018 at 6:18 AM Venkat Dinavahi<EMAIL_ADDRESS>wrote:

Great! That's a good point. Alternatively we could call the property
apolloClient.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/bgentry/ember-apollo-client/pull/103#issuecomment-376521362,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG9cbACo9OObk8kDt3i_p1PvJKxDpXSks5tijwNgaJpZM4SPYom
.


sync remote selection

Fixes https://github.com/excalidraw/excalidraw/issues/1109
First take. Will refactor tomorrow.
(The stroke rendering courtesy of @vjeux)

Related: I think we should use a subset of bright colors for remote users. I often get gray/dark-blue/purple remote color which is hardly distinguishable from local color (black).

Btw, sometimes the selection renders, but not the element (on remote). Happens usually during init. Can't repro easily, so it's hard to debug. Don't think it's related to this PR as I've been seeing invisible (i.e. unsynced) elements when I worked on collab earlier.

We should probably remove the white from the pool:

How do you feel about having nested solid focus-outline-style selection instead of indicating using dashed lines?

I kind of like the current behaviour.. if more than two it doesn't really matter anyway who is touching it.. and looks cool!

I'm playing with it right now and the current dashed line behavior looks a bit weird. But not sure if it's because I'm just playing alone.
I feel like it's worth shipping right now as it's working and we can tweak the rendering later. Should be pretty easy.

Agree..
Make it work, then make it better!


Default configuration file is not used/found in a Composer installed project

Bug report
An existing configuration file .php-cs-fixer.dist.php in the root directory of an installed Composer project is not used/found when php-cs-fixer is used via ./vendor/bin/php-cs-fixer:
$ ./vendor/bin/php-cs-fixer fix --dry-run -v
PHP CS Fixer 3.0.0-beta.2  by Fabien Potencier and Dariusz Ruminski
Runtime: PHP 7.4.16
Loaded config default.

In Finder.php line 611:

  [LogicException]
  You must call one of in() or append() methods before iterating over a Finder.

A workaround is to explicitly set the --config parameter:
$ ./vendor/bin/php-cs-fixer fix --dry-run -v --config .php-cs-fixer.dist.php
PHP CS Fixer 3.0.0-beta.2  by Fabien Potencier and Dariusz Ruminski
Runtime: PHP 7.4.16
Loaded config default from ".php-cs-fixer.dist.php".
.....                                                                                5 / 5 (100%)
Legend: ?-unknown, I-invalid file syntax (file ignored), S-skipped (cached or empty file), .-no changes, F-fixed, E-error

Checked all files in 0.014 seconds, 16.000 MB memory used

php-cs-fixer v2 works as expected:
$ ./vendor/bin/php-cs-fixer fix --dry-run -v
PHP CS Fixer 2.19.0 Testament by Fabien Potencier and Dariusz Ruminski
Runtime: PHP 7.4.16
Loaded config default from "/Users/foo/my-project/.php-cs-fixer.php".
.....
Legend: ?-unknown, I-invalid file syntax (file ignored), S-skipped (cached or empty file), .-no changes, F-fixed, E-error

Checked all files in 0.025 seconds, 16.000 MB memory used

You are using 3.0.0-beta.2 where the new config file name is not available, update to 3.0.0 and it will work.

Same here using 2.19.0, but I will update in a near future.


[FEATURE REQ] support cadl sync and generate for Java SDK

ref: https://github.com/Azure/azure-sdk-tools/pull/5272/files (scripts are syned to sdk repo)
Our first case can be MVAD https://github.com/Azure/azure-rest-api-specs/tree/main/specification/cognitiveservices/AnomalyDetector
(you can use other case)
We do not need to able to run automation or CI on it.
First we probably just want to add the cadl-location.yaml, and able to locally run the PS script to generate the code.
Later we can worry about automation or other script for first-time SDK onboard (client_version.txt, ci.yml, pom.yml etc.)
Feel free to collaborate with @XiaofeiCao as he might be more familiar with SDK repo scripts.

sdk repor pr ref: https://github.com/Azure/azure-sdk-for-java/pull/33251

PS: also evaluate on whether it may be integrated in CI
e.g. https://github.com/Azure/azure-sdk-for-java/pull/32498 this one for swagger/readme.md

official spec guide is here https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/cadl-structure-guidelines.md
please make a short paragraph to guide service to use the script from SDK repo.
Plan to insert that into https://github.com/Azure/azure-sdk-for-java/wiki/Cadl-Java-Quickstart#use-cadl (before that section, as recommend service to do this together with their spec repo)

in>
Regarding to integrating the script in CI, there are two places to run the script.
One is to have a seperate CI running on merged branch(usually main branch) like lite gen CI. So we can just generate sdk using CI instead of generating locally. The CI will:

sync cadl and generate sdk
create pr in azure-sdk-for-java repo.

The other is to trigger the script in pr. But I can't think of a meaningful use case.
Please let me know your thoughts on where to run the scripts in CI.

The CI step Alan did, was to make sure the code is always latest (from codegen), before release etc.
We don't need a fluent lite gen CI. Data-plane PR is done by service, and they can use the automation from spec to do the PR. They don't need to first configure spec repo, then get to SDK repo do generate code.

First let's get MVAD regened and we can get it merged.

First let's get MVAD regened and we can get it merged.

Got it, make sense, working on it now.


vehicle-purchase concept exercise

For conditionals. Concept will follow in the next PR.

Every track has a nightmare with cyclic dependencies in the learning syllabus as they try to sequence exercises, and this is also true here. My thinking, rightly or wrongly, was that the first 3 concepts follow a sequence that students are familiar with from other tracks, then in concept 4 (vectors) we start to move to idiomatic R. I cheated a bit in exemplar.R and used c(), but this isn't essential.
I just re-read the Exercism documentation on syllabus design. They explicitly encourage hand-waving:
"Sometimes you'll feel like there is a deadlock. Concept A requires understanding concept B, and B requires understanding A.
In this case simplify. Hand-wave over some complexity in one so that you can get students familiar with the other. It's perfectly fine to say that something will be introduced in more depth later, and that for now the student just needs to understand this one bit.
Concepts are understood more deeply in stages and over time."
That could, of course, be used as an argument for conditionals before or after vectors!
I'm normally uncomfortable with evading making a decision (former research manager speaking), but might this be a good point to flag up the issue and solicit opinions from other maintainers? In preparing teaching materials, how they are perceived by others is pretty much the point.

Thinking about this a bit more, maybe it's the exercise that is wrong for the concept, rather than concept sequencing?
Would conditionals before vectors work better if cars-assemble introduced it (#264)?

Cool - points well made and I understand that some deadlocks will be unavoidable.
I agree that it probably makes sense to introduce the first few concepts in a similar order to what many other tracks do, so maybe deferring vectors slightly is the right call.
cars-assemble feels slightly cleaner and better to me for introducing the conditionals concept because it doesn't involve vectors. The exercise is obviously more mathematical (which might be perceived as more difficult), but since R is well suited to numeric problems I think in general it may make sense to lean into these sorts of examples to illustrate concepts.
Would you be happy to swap out cars-assemble for vehicle-purchases?

Absolutely, no problem.


Fix Array length when window its to small

Uses a minimum valid value for creating array instances, fixes #130 and #283(from Lerna project).
Thanks @thejameskyle for the inspiration and you guys for the library 🚀

@thebigredgeek thanks for merging! Do you think we can do release with the changes? that would be great :)


react-native panresponder onPanResponderMove possible bug or improvement needed + documentation needed

i wrote a stackoverflow but I believe this to be an unintended behavior/bug
http://stackoverflow.com/questions/41586276/react-native-onpanrespondermove-strange-behavior-no-documentation-animated-event
Description
I want to have a pan responder I can drop and focus on child elements. When I use the syntax
onPanResponderMove: Animated.event([null, {dx: this._pan}]),
Animated.event does call this._pan however if I use
onPanResponderMove: (e, gestureState) => {
Animated.event([null, {dx: this._pan}])
},
such a syntax does not get called even though it is the recommended usage in the docs. Animated.event just doesn't call on drag.
Reproduction
https://github.com/Kielan/rn_emoji_test
Not sure how to fix this I just want to start the discussion and get more documentation on panresponder.
Additional Information

React Native version: latest
Platform:  iOS simulator
Operating System: MacOS osx

Hey, I answered you question on SO.
As for documentation, all the examples seem to have no wrapping in them. A note on applying might be useful though.

@facebook-github-bot answered

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


[Suggestion] Option to sort branches alphabetically

Great add-on, works like a charm on Manjaro Linux!
I came here to ask whether you have any influence on the order of the branches. If yes, an option to sort them by their unicode values (alphabetically) like on the sidebar would be a nice feature.
As you can see in this example deck, the numbered leafs appear in random order:

Good idea, I made sorted branches the default now (f008aea9276a442cc521525f3337c750ef27b631). The new version is already on AnkiWeb.

Thanks for the quick response, looking good!