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
I cannot connect to the docker-socket-proxy when it is running on another host. I am using this docker-compose setup to run the proxy on the remote host:
It does start as expected when running sudo docker-compose up and I can register it as a deploy daemon in my Nextcloud server. However, when I run the Test deploy for the daemon it fails at stage Heartbeat. It does install the test deploy container on the remote host and is able to start it:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
299ce125b19f ghcr.io/cloud-py-api/test-deploy-cpu:release "python3 main.py" 10 minutes ago Up 10 minutes (healthy) nc_app_test-deploy
1464ca39de38 ghcr.io/cloud-py-api/nextcloud-appapi-dsp:release "/bin/bash start.sh" 6 days ago Up 11 minutes (healthy) nextcloud-appapi-dsp
Still, Nextcloud server cannot connect to it. If I check the open ports on the remote host running the proxy with sudo netstat -tulpn | grep LISTEN, I get this:
I guess the open port in the fourth line should be 192.168.178.23000 for the Heartbeat to work properly?
The Nextcloud server and the remote host are on the same network 192.168.178.0/24 and there is no firewall that could prevent any traffic. The remote host is a Raspberry Pi3 running Raspbian (it is setup for testing purpose only, I realize it is not a suitable platform to run the ExApps in a productive manner). It also does not help if I change the env variable for the sub containers according to the readme: - EX_APPS_NET="ipv4@127.0.0.1"
If the failing Heartbeat is not an issue of the docker-socket-proxy but my setup is messed up, any hint will be highly appreciated.
The text was updated successfully, but these errors were encountered:
I cannot connect to the docker-socket-proxy when it is running on another host. I am using this docker-compose setup to run the proxy on the remote host:
It does start as expected when running
sudo docker-compose up
and I can register it as a deploy daemon in my Nextcloud server. However, when I run the Test deploy for the daemon it fails at stage Heartbeat. It does install the test deploy container on the remote host and is able to start it:Still, Nextcloud server cannot connect to it. If I check the open ports on the remote host running the proxy with
sudo netstat -tulpn | grep LISTEN
, I get this:I guess the open port in the fourth line should be
192.168.178.23000
for the Heartbeat to work properly?The Nextcloud server and the remote host are on the same network
192.168.178.0/24
and there is no firewall that could prevent any traffic. The remote host is a Raspberry Pi3 running Raspbian (it is setup for testing purpose only, I realize it is not a suitable platform to run the ExApps in a productive manner). It also does not help if I change the env variable for the sub containers according to the readme:- EX_APPS_NET="ipv4@127.0.0.1"
If the failing Heartbeat is not an issue of the docker-socket-proxy but my setup is messed up, any hint will be highly appreciated.
The text was updated successfully, but these errors were encountered: