Search found 7 matches
- 10 Nov 2021, 22:08
- Forum: Ubuntu & Desktop Linux
- Topic: [aarch64] Can't start filebot-xpra docker container
- Replies: 6
- Views: 13397
Re: Can't start filebot-xpra docker container
Running as a root brings new problems, which I did not investigate further: ubuntu@ubuntu:~$ docker run --rm -it -e PUID=0 -e PGID=0 -v $PWD:/volume1 -v data:/data -p 5454:5454 rednoah/filebot:xpra + xpra start --start-child=filebot --exit-with-children --bind-tcp=0.0.0.0:5454 --tcp-auth=none --daem...
- 07 Nov 2021, 22:21
- Forum: Ubuntu & Desktop Linux
- Topic: [aarch64] Can't start filebot-xpra docker container
- Replies: 6
- Views: 13397
Re: Can't start filebot-xpra docker container
In the meantime, I read a little bit more in the xpra docus and especially the python-uinput does not seem to be important. See https://xpra.org/trac/wiki/FAQ for more information. It seems that my main problem was an access rights problem. I can successfully start the container with docker run --rm...
- 01 Nov 2021, 17:48
- Forum: Ubuntu & Desktop Linux
- Topic: [aarch64] Can't start filebot-xpra docker container
- Replies: 6
- Views: 13397
Re: Can't start filebot-xpra docker container
I didn't have time to look into the problem in the last days. Today, I wanted to, but the situation changes completely. I assume this is due to your commits - 0fad2a9a1d0c19c130d7b023cf016075e2c4d414, which creates the folder I mention in my error log. - afd2795ec625b0f630ab9cd01e3b8803da56fcdd, whi...
- 19 Oct 2021, 17:22
- Forum: Ubuntu & Desktop Linux
- Topic: [aarch64] Can't start filebot-xpra docker container
- Replies: 6
- Views: 13397
[aarch64] Can't start filebot-xpra docker container
Hello, I can't start the filebot-xpra docker container on my Pi 4. The following console interaction shows what happens and the error messages I receive: ubuntu@ubuntu:~/repos/filebot-docker$ docker run --rm -it -v $PWD:/volume1 -v data:/data -p 5454:5454 rednoah/filebot:xpra + xpra start --start-ch...
- 19 Oct 2021, 17:16
- Forum: Ubuntu & Desktop Linux
- Topic: [FileBot Node] --optimize_for_size causes Bus error (core dumped) crash
- Replies: 5
- Views: 9657
Re: Can't start filebot-node docker
Via some further experimenting, I found a solution. I only had to do one change in the file node/opt/filebot-node/start : -exec node --optimize_for_size "/opt/filebot-node/server/app.js" +exec node "/opt/filebot-node/server/app.js" However, I did not try to find out why the optim...
- 18 Oct 2021, 19:48
- Forum: Ubuntu & Desktop Linux
- Topic: [FileBot Node] --optimize_for_size causes Bus error (core dumped) crash
- Replies: 5
- Views: 9657
Re: Can't start filebot-node docker
First, thank you very much for your response. I deleted all images using : docker rmi -f $(docker images -a -q) Afterwards, I also checked that all images are gone. Then, I tried: docker run --rm -it -v $PWD:/volume1 -v data:/data -p 5452:5452 rednoah/filebot:node The behavior did not change - there...
- 17 Oct 2021, 18:58
- Forum: Ubuntu & Desktop Linux
- Topic: [FileBot Node] --optimize_for_size causes Bus error (core dumped) crash
- Replies: 5
- Views: 9657
[FileBot Node] --optimize_for_size causes Bus error (core dumped) crash
Hello, I can't start the filebot-node docker and I'm completely lost, as there is not output anywhere. I use a Pi 4 and run a non-root docker. I tried the following commands: docker run --rm -it -v /mnt/exthdd/plexLibrary:/volume1 -v data:/data -p 5452:5452 rednoah/filebot:node docker run --rm -it -...