Opening container's console

[shalafi99]

Hello, appreciated if some pointers could be provided on what I missed here.

I changed EXEC to 1 in the socket environment but when I try to launch the console for a running container, I just get a blinking prompt (until it times out).
The logs displayed this during an attempt to grab the console:

2024-08-28 11:49:16 ::ffff:172.18.0.4:52648 [28/Aug/2024:14:49:16.054] dockerfrontend dockerbackend/dockersocket 0/0/0/16/32 201 276 - - ---- 4/4/3/3/0 0/0 "POST /containers/44394f4c848823efd5c9c012373446de8c101cba679c810dae4fca09329634eb/exec HTTP/1.1"
2024-08-28 11:49:16 ::ffff:172.18.0.4:52648 [28/Aug/2024:14:49:16.512] dockerfrontend dockerbackend/dockersocket 0/0/0/8/9 200 169 - - ---- 5/5/4/4/0 0/0 "POST /exec/8f041ceb2129cbb18b0618986a483deeea979e957bbc151b400e4f82dd7e2e19/resize?h=31&w=175 HTTP/1.1"
2024-08-28 11:49:16 ::ffff:172.18.0.4:52648 [28/Aug/2024:14:49:16.910] dockerfrontend dockerbackend/dockersocket 0/0/0/16/17 200 169 - - ---- 5/5/4/4/0 0/0 "POST /exec/8f041ceb2129cbb18b0618986a483deeea979e957bbc151b400e4f82dd7e2e19/resize?h=30&w=174 HTTP/1.1"

I am experimenting with two separate proxy-sockets, one for Portainer and other for Dockge, the behavior is the same on both platforms while trying to open a console.
From Docker itself it works as expected, as it also did before while I was using Portainer and Dockge connected directly to the docker socket.
Not using Swarm.

The log shows me EXEC is being allowed, right? (as expected before changing it to 1, I would get "403 forbidden" as a response from the socket when EXEC=0)
Are other API sections involved in this type of action, aside from EXEC?
The ones I have allowed are:

• POST=1
• CONTAINERS=1
• IMAGES=1
• INFO=1
• NETWORKS=1
• SERVICES=1
• TASKS=1
• VOLUMES=1
• EVENTS=1
• PING=1
• VERSION=1
• EXEC=1

Thank you

[shalafi99]

After updating the proxy containers to version 0.3.0, I discovered that the consoles started to launch correctly again.