Is there a known issue with using the same-system docker compose script with portainer?

[Cereal916]

If I change the beszel host - network_mode: host - then everything works fine, but I'm not getting a connection when I use the provided script and adding host.docker.internal on the "Add New System" form.

provided script:
https://github.com/henrygd/beszel/blob/main/supplemental/docker/same-system/docker-compose.yml

Any ideas on what I could be doing wrong? I dont see any errors in the host or agent logs.

[henrygd]

Nothing specific to Portainer that I know of, but there was a recent issue (#359) on NixOS that turned out to be firewall related.

Try checking the /_/#/logs page for errors and see if you can connect from the host with telnet localhost 45876.

[Cereal916]

It wont let me open that container console in portainer for some reason. Let me figure out the command line argument and try that way.

[Cereal916]

Trying to exec in didnt work either
OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

[Cereal916]

port 22 appears to be blocked, so cant ssh in either.

[Cereal916]

Sorry, I'm just now realizing that is a path on the ui. There are no errors on that page.
When I run telnet localhost 45876 from my server it appears to connect successfully.

[henrygd]

Sorry, there's no shell in the container so you can't use exec. I can give you a dockerfile tomorrow if you want to build it with Alpine or Debian to troubleshoot.

Can you double check that you used host.docker.internal (not localhost) as the value in the "Host / IP" field when adding the system?

Also that you updated the KEY value in the compose config with the value given to you in the 'Add System' dialog?

[Cereal916]

I'm seeing lots of stuff on stack-overflow about this just not being supported on linux, perhaps that is the case. Maybe a simpler solution would be to provide a field on the docker compose yaml that tells the beszel host what port to run on? My current issue is I already have something running natively on 8090 and was trying to avoid reconfiguring my other app.

[henrygd]

Change the first port number specified in the compose file. So instead of 8090:8090 you can use 8091:8090 to run on port 8091.