Problems running on Docker, maybe NAS

[elonen]

(Converted to a support thread for @krth8)

[krth8]

Hi!

Just stumbled upon this very interesting looking tool!

We are a small Film/VFX shop and would love to try this on our Synology through docker.

When installing the latest version from the registry i am getting some error messages (which i am sure is user error)

Would love to get some pointers here! 🥇

elonen-clapshot1

date	stream	content
2023-03-27T09:02:50.499565624Z	stdout	tail: no files remaining
2023-03-27T09:02:50.499465184Z	stdout	tail: cannot open '/var/log/clapshot.log' for reading: No such file or directory
2023-03-27T09:02:50.484759368Z	stdout	tail -f /var/log/clapshot.log
2023-03-27T09:02:50.484706586Z	stdout	# Follow server log
2023-03-27T09:02:50.484577672Z	stdout
2023-03-27T09:02:50.484080606Z	stdout	sudo -u docker $CMD &
2023-03-27T09:02:50.480072167Z	stdout	CMD=$(grep 'Exec' /lib/systemd/system/clapshot-server.service | sed 's/^.*=//')
2023-03-27T09:02:50.480005124Z	stdout	# Dig up start command from systemd script and run it as docker user instead of www-data
2023-03-27T09:02:50.479965386Z	stdout
2023-03-27T09:02:50.479926833Z	stdout
2023-03-27T09:02:50.479885517Z	stdout	EOF
2023-03-27T09:02:50.479844956Z	stdout	==============================================
2023-03-27T09:02:50.479789019Z	stdout	---  Browse http://127.0.0.1:8080  ---
2023-03-27T09:02:50.479751128Z	stdout
2023-03-27T09:02:50.479711845Z	stdout	|_|
2023-03-27T09:02:50.479671282Z	stdout	| |
2023-03-27T09:02:50.479628990Z	stdout	_||_,| ./||| ||___/ __|
2023-03-27T09:02:50.479587392Z	stdout	| || | (| | |) _ | | | | () | |_
2023-03-27T09:02:50.479541424Z	stdout	| |    | |/ ` | ' / _| ' \ / _ | __|
2023-03-27T09:02:50.479499750Z	stdout	| |    | | __ _ _ __  | |   ___ | |
2023-03-27T09:02:50.479453844Z	stdout	/ _| |               | |   |/ | |
2023-03-27T09:02:50.479411948Z	stdout	_____ _                 _     __/ | _
2023-03-27T09:02:50.479370045Z	stdout	||  __,|| ||| |||| ||__, |
2023-03-27T09:02:50.479329968Z	stdout	| | \ | || | | | | | | | | | | | (| |
2023-03-27T09:02:50.479287140Z	stdout	|  _  | | | | '_ | '_ | | '_ \ / _` |
2023-03-27T09:02:50.479239386Z	stdout	| |__) _   _ _ __  _ __  _ _ __   __ _
2023-03-27T09:02:50.479195661Z	stdout	|  __ \                 (_)
2023-03-27T09:02:50.479143665Z	stdout	_____                   _
2023-03-27T09:02:50.478981942Z	stdout	==============================================
2023-03-27T09:02:50.478723696Z	stdout	echo <<- "EOF"
2023-03-27T09:02:50.478570814Z	stdout
2023-03-27T09:02:50.200938486Z	stdout	chown: cannot access '/mnt/clapshot-data/data/clapshot.log': No such file or directory
2023-03-27T09:02:50.200116670Z	stdout	touch: cannot touch '/mnt/clapshot-data/data/clapshot.log': No such file or directory
2023-03-27T09:02:50.198383631Z	stdout	chown: cannot access '/mnt/clapshot-data/data': No such file or directory
2023-03-27T09:02:50.193589032Z	stdout	sed: -e expression #1, char 32: unknown option to `s'

[elonen]

Hi. This doesn't show how exactly you started the Docker image, but based on cannot access '/mnt/clapshot-data/data': No such file or directory, I'd say your start command probably didn't mount a volume/directory at /mnt/clapshot-data. The server needs it to store videos, database etc.

[krth8]

Thanks for the swift reply!

I have now tested creating the volume at root, and in the clapshot folder in the docker root. I guess this is the wrong way to do it? 📦

/docker/elonen-clapshot1/mnt/clapshot-data

and

/mnt/clapshot-data

[elonen]

There are basically two ways of mounting data directories on Docker:

1. volumes (not fast to explain, google this)
2. bind mounts to local directories

Option 2 is what the example makefile uses. Here's roughly how to mimic it:

docker run --rm -it -p 127.0.0.1:8095:8095 --mount type=bind,source="$(pwd)/my_data_dir",target=/mnt/clapshot-data  clapshot:latest-demo

This will mount your local directory ./my_data_dir to /mt/clapshot-data inside the Docker image.

Based on the log you pasted, it looks like you are using one of the startup scripts from test/ pretty much as is. If you look inside it, you'll notice that it uses DIR="/mnt/clapshot-data/data", so you might need to mkdir ./my_data_dir/data before running Docker with a command similar to the one I wrote above. Alternatively, you could probably just change the DIR to DIR="/mnt/clapshot-data". (Maybe I'll remove the extra data/ from the next release, it's there just to

If you are trying to get this running on a NAS device (Synology) using the docker demo image (which is preconfigured for running on your local computer), you'll probably next bump into the following issues:

• You'll need to bind port 8095 to 0.0.0.0 instead of 127.0.0.1. Otherwise you could only connect from the NAS itself. Change the Docker command to fix this.
• You'll need to point the client to make websocket connection to something like "my-nas:8080/", not "127.0.0.1:8080". In the test/ scripts you are apparently using, it's variable URL_BASE.

[elonen]

Ah, sorry, now I see what the problem is here.

I'm using port 8095 as an API port, and for local development without Nginx, but you are in fact running the demo container. It makes a full Debian image and serves Clapshot API through an Nginx reverse proxy, as is recommended for production. Nginx, in this setup, listens to standard HTTP port 80 inside the container, so you'll need to expose it instead.

Remove the 8095->8095 binding, and instead do 80->8080. Your screenshot should then show something like

Ports
  80/tcp       127.0.0.1:8080

Then browse http://127.0.0.1:8080/

As you can see from the log, API internally still listen at 8095, but Nginx forwards Websocket requests from your browser (standard port 80) to it like so:

server {
        ...
	listen 80 default_server;
	listen [::]:80 default_server;
        ...
		location /api {
			proxy_pass http://127.0.0.1:8095/api;

			# Also pass along websocket
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection "Upgrade";
			proxy_set_header Host $host;

[krth8]

Thanks!!

I did this run command:

docker run --rm -it -p 127.0.0.1:8080:80 --mount type=bind,source="$(pwd)/my_data_dir",target=/mnt/clapshot-data elonen/clapshot:latest-demo

And now i can browse! Ui is nice and really responsive.

Will try getting the auth version working and then on the Synology. This could be really useful for us.

[elonen]

Let me know how it goes. I didn't really intend the demo Docker container to be used for production deployments, mainly because it doesn't really easily allow custom configuration or HTTPS. I can see though, that it might be useful for some small installations - perhaps with some modifications.

[elonen]

Another issue I can see in running this on a NAS, is video transcoding. By default, Clapshot server will currently transcode any videos with bitrate over ~2.5Mbps, or codec that isn't one of ["h264", "avc", "hevc", "h265"], or container that isn't ["mp4", "mkv"]. That's because your browser will need to be able to play the file.

You'll probably want to upload videos that already adhere to these specs, as NAS devices aren't usually very suitable for video compression.

[krth8]

Yes. Just testing and will try out the deployment version later on. We are mainly artists with lacking skills in the IT department.

I figured as well that the transcoding would be slow on the NAS, and would for sure benefit from being run on a dedicated computer. Pretty sure that's the route.

Thanks a lot for the assistance. Looking forward to see what more you can do with this project!