You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating a docker from another platform such as portainer or ssh, in dockge appears as inactive when it has already been restarted again whit new image.
When in Portainer is running
👟 Reproduction steps
Start dockge and show the docker screen, in parallel from another window, update the container, in dockge you can see how the container stops in your terminal, but while is updating and restart, dockge no longer updates the terminal.
Even after restarting dockge it still appears as inactive.
It is necessary to press the start button in the dockge and then set it to running
👀 Expected behavior
auto refresh docker status or with button
😓 Actual Behavior
Dockge Version
1.4.1
💻 Operating System and Arch
windows 11 - Nas Synology
🌐 Browser
Firefox
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
Description
After updating a docker from another platform such as portainer or ssh, in dockge appears as inactive when it has already been restarted again whit new image.
When in Portainer is running
👟 Reproduction steps
Start dockge and show the docker screen, in parallel from another window, update the container, in dockge you can see how the container stops in your terminal, but while is updating and restart, dockge no longer updates the terminal.
Even after restarting dockge it still appears as inactive.
It is necessary to press the start button in the dockge and then set it to running
👀 Expected behavior
auto refresh docker status or with button
😓 Actual Behavior
Dockge Version
1.4.1
💻 Operating System and Arch
windows 11 - Nas Synology
🌐 Browser
Firefox
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: