-
I updated to the latest image today and the container refuses to start. Oddly, I cannot even restart or remove the container except through Portainer. I've restarted Docker, restarted the server, and deleted the image and rebuilt the project, but it refuses to start. If there anything that I should do or is there an issue with the latest image? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
I have the same problem getting this error log: "ERROR no iptables supported found: errors encountered are: iptables-nft: iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument (exit status 4); iptables: iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument (exit status 4)" |
Beta Was this translation helpful? Give feedback.
-
I'm seeing the same error in the logs. I've now submitted an issue. |
Beta Was this translation helpful? Give feedback.
-
I have the exact same issue |
Beta Was this translation helpful? Give feedback.
-
Same here. Reverted to a previous release just to have a running container. |
Beta Was this translation helpful? Give feedback.
-
This is fixed in 26705f5 |
Beta Was this translation helpful? Give feedback.
This is fixed in 26705f5