elonen
commented
1 month ago Do you have a modified docker-entry_htadmin.sh and/or Docker image? Wondering how did URL_BASE become http://192.168.0.20:8080 . Another odd thing about the log is CORS origins [""] (should be ["*"] in the demo image). The python errors seem to suggest that clapshot-server.conf in the image already has a cors=... entry, and the entry script then adds another one, leading to the arg parser error.
That aside, do you have a clear idea on how exactly should a Docker-based production deployment to work? E.g. HTTPS cert management, config file, logging, storage. I almost never use Docker for production myself, so I'm not really familiar with the best practices.
krth8
Hi,
The demo is stuck on "Connecting server"
Both server and image would run of the same machine.
[12:03:27 PM] Auth error at 'http://192.168.0.20:8080/api/health': 502 - Bad Gateway`clapshot-1 | --- Browse http://192.168.0.20:8080/ for Clapshot clapshot-1 | --- or http://192.168.0.20:8080/htadmin/ for user management clapshot-1 | --- clapshot-1 | --- Default users: clapshot-1 | --- - admin:admin (can edit other people's videos) clapshot-1 | --- - demo:demo clapshot-1 | --- - alice:alice123 clapshot-1 | --- clapshot-1 | --- User management admin: clapshot-1 | --- - htadmin:admin (only for /htadmin) clapshot-1 | ============================================================== clapshot-1 | clapshot-1 | # Dig up start command from systemd script and run it as docker user instead of www-data clapshot-1 | CMD=$(grep 'Exec' /lib/systemd/system/clapshot-server.service | sed 's/^.=//') clapshot-1 | sudo -u docker $CMD & clapshot-1 | clapshot-1 | # Follow server log clapshot-1 | tail -f /var/log/clapshot.log clapshot-1 | 2024-05-21T09:59:33+00 INFO ORG: [stdout] [bf.after_migration] Running post-migration checks... clapshot-1 | 2024-05-21T09:59:33+00 INFO srv->org handshake done (org->srv not connected yet). clapshot-1 | 2024-05-21T09:59:33+00 INFO Starting video processing pipeline. clapshot-1 | 2024-05-21T09:59:33+00 INFO MD: Starting. n_workers=4 clapshot-1 | 2024-05-21T09:59:33+00 INFO INCOMING: Starting. dir="/mnt/clapshot-data/data" poll_interval=3.0 resubmit_delay=15.0 clapshot-1 | 2024-05-21T09:59:33+00 INFO COMPR: Starting. n_workers=8 clapshot-1 | 2024-05-21T09:59:33+00 INFO API: org->srv connected, bidirectional gRPC established. org_name="clapshot.organizer.basic_folders" description="Basic folders for the UI" version="0.6.1" clapshot-1 | 2024-05-21T09:59:33+00 INFO API: Starting frontend API server. port=8095 clapshot-1 | 2024-05-21T09:59:33+00 INFO API: Allowed CORS origins: [""] clapshot-1 | 2024-05-21T09:59:33+00 WARN API: !! SECURITY RISK !! – Using CORS origin '' allows any website to access your video annotation system. This exposes your users' videos to potential API attacks. Do NOT use '' in production! Instead, specify the allowed origin, such as 'https://clapshot.example.com'. clapshot-1 | Traceback (most recent call last):
clapshot-1 | File "", line 3, in
clapshot-1 | File "/usr/lib/python3.11/configparser.py", line 713, in read
clapshot-1 | self._read(fp, filename)
clapshot-1 | File "/usr/lib/python3.11/configparser.py", line 1112, in _read
clapshot-1 | raise DuplicateOptionError(sectname, optname,
clapshot-1 | configparser.DuplicateOptionError: While reading from '/etc/clapshot-server.conf' [line 59]: option 'cors' in section 'general' already exists
clapshot-1 | [1m[31merror:[0m the following required arguments were not provided:
clapshot-1 | [32m--data-dir [0m
clapshot-1 | [32m--url-base [0m
clapshot-1 |
clapshot-1 | [1m[4mUsage:[0m [1mclapshot-server[0m [1m--data-dir[0m [1m--url-base[0m
clapshot-1 |
clapshot-1 | For more information, try '[1m--help[0m'. ` Would love for this to work, Also, a docker image suitable for production would be real neat.