Last docker container "installed" is the Plex server...
But there's no sense that a docker container is freezing the complete system
Last docker container "installed" is the Plex server...
But there's no sense that a docker container is freezing the complete system
Hi, I didn't said that my SD card is corrupted...
When I reboot the RPI it works fine...
But LE is freezing often...
Hi,
My LE 8.95.003 is freeking quite often (allmost each day, the first time I am trying to access) on my Rpi 3 ==> only solution is removing power supply with the risk to corrupt SD card
the rpi is replying to ping... but not to ssh or samba... and if I look on tv side, the display is frozen...
I am not doing very special things... just running LE and some docker containers (transmission and Plex server)
Any idea where it's coming from ?
Thank you chewitt.
Nobody tried ?
Or nobody has a script-only solution to shutdown RPI when connected to UPS ?
Hi all,
I have connected my RPI3 and my external HD to a APC UPS in order to avoid corrupted SD card...
Is there a way of using the apcupsd daemon with LE ? APCUPSD User Manual
Thank you,
Ok... corrected...
I had to disable the service and to re-enable it in order to recreate the symlink...
Hi all, I moved my transmission Docker to a new rpi3 with the new version of LibreELEC and now I have a storage issue...
Since I use the same configuration files that for my legacy rpi2... And same usb storage for all incomplete / complete files.... There's no sense...
Any idea?
Sent from my SM-A510F using Tapatalk
Thank you, I have seen this yesterday night and now everything is working fine again
Sent from my SM-A510F using Tapatalk
Hello my transmission with Docker does not work anymore after the update took the last version of LibreELEC.
This is the error message :
Unit service.system.docker.service not found
Sent from my SM-A510F using Tapatalk
Hi, I have a working setup using Docker on Rpi 2... LibreELEC
With transmission, couchpotato and sickgear...
Sent from my Nexus 5 using Tapatalk
Arghhh new story, tonight... I don't know why... but it works... without having done anything...
LibreELEC:~ # docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
db8e79d75f38 libreelecarm/transmission "/start.sh" 12 hours ago Up 12 hours 0.0.0.0:9091->9091/tcp, 0.0.0.0:45555->45555/tcp transmission
And he has grabbed all the thing that was put in my wath folder by sickgear...
I imagine that at a tiime, the port 45555 was released by docker and so, system.d has created the container...
Now, I have launched a test of 2Go... to verifiry that nothing is stored on the SD card... and after I reinstall sickgear... even if I don't see french-speaking trackers...
I have tried to unistall/re-install Docker... nothing change.
I have tried to change the port 45555 to 5555 (in transmission.service, settings.json and Dockerfile) and this is the result:
Quote
time="2016-08-01T09:56:30.193078160+02:00" level=error msg="Handler for POST /v1.24/containers/f65578749469074ff874f7be40409e0
46d1aa3791d93a03c9895c7b65696ce45/start returned error: oci runtime error: process_linux.go:334: running prestart hook 0 caused \"fork/exec /storage/.kodi/addons/servic
e.system.docker/bin/dockerd (deleted): no such file or directory: \
==> I imagine that it is not the right way...
I found the logs... in journalctl
and the error is coming from the port 45555:
Jul 31 23:55:38 LibreELEC dockerd[14117]: time="2016-07-31T23:55:38.043808723+02:00" level=error msg="Handler for POST /v1.24/containers/a52685cd7c24ee39393f6c04feb9550
a63d813906cb3141893308d0431214463/start returned error: driver failed programming external connectivity on endpoint transmission (5e88d063a02a85c00d73c8b6317764e4b5b0b3
929fa193659693d7723e895e30): Bind for 0.0.0.0:45555 failed: port is already allocated"
Jul 31 23:55:38 LibreELEC docker[20809]: /storage/.kodi/addons/service.system.docker/bin/docker: Error response from daemon: driver failed programming external connecti
vity on endpoint transmission (5e88d063a02a85c00d73c8b6317764e4b5b0b3929fa193659693d7723e895e30): Bind for 0.0.0.0:45555 failed: port is already allocated.
Jul 31 23:55:38 LibreELEC systemd[1]: [[0;1;39mtransmission.service: Main process exited, code=exited, status=125/n/a[[0m
strange thing since I have restarted the docker service mutliple times... and even rebooted the host...
And I do not see anything in netstat...
Where may I find any logs of the container creation?
Sent from my Nexus 5 using Tapatalk
Arghhh... tonight I don't understand anything...
Nothing is working anymore...
The last thing I had done was to remove the download in error in transmission...
After that, I connect myself in ssh... in order to try to find a solution (see the previous post) and nothing is working anymore... No transmission, no sickgear...
I had a message from docker when trying a
something like client version higher than server version...
So I decided to simply reboot the Rpi.(with the simple reboot console command).. and after the reboot... no error on docker info (3 containers stopped)..
So I have tried a lot of things... even
[code]
docker stop $(docker ps -a -q) docker rm $(docker ps -a -q)
systemctl enable /storage/Dockerfiles-master/arm/transmission/tran
smission.service
systemctl start transmission
[/code]
And nothing is working...
When I do docker ps... after some seconds I see transmission... but if I recheck, docker ps => empty
and
HELP !
Remark: I always have
LibreELEC:~ # systemctl enable /storage/Dockerfiles-master/arm/transmission/tran
smission.service
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
Display More
But even with this message, it was working "fine"
Hello,
On my side, the installation and so on was looking good and so I did a test with a "small" file of 200Mb... and ... at the end, the downloaded file was on my download folder on my external HD... so perfect...
After more tests and the configuration of the sickgear docker... I see two problems:
1. When I try to downlad larger file, I have an error message "no space left on device"... so I imagine that somewhere he is storing something on the SD card...
2. When sickgear is storing something on my watch-dir (on the external HD)... transmission is just doing nothing.
Any idea ?
This is my service code
ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker run \
--rm \
--name=%p \
--hostname=libreelec-%p \
--volume=/var/media/external_HD/%p/watch:/watch \
--volume=/var/media/external_HD/%p/downloads:/downloads \
--volume=/var/media/external_HD/%p/incomplete:/incomplete \
--volume=/storage/%p/config:/config \
--publish=9091:9091 \
--publish=45555:45555 \
libreelecarm/%p
Display More
Thank you,
Well you obviously missed the multiple other threads about transmission on this board.
Yes... I missed it... and had launched the upgrage a little bit too fast...
I am currently trying to get it working with Docker... using thi thread: LibreELEC
but not successfully... Docker is always trying to start the service...
[hr]
Ok... it's working fine with Docker...
My next issue is samba... I don't know why but I have authentication issue...
[hr]
OK.... Samba fixed... my fault... user/pass were openelec... (I think I need to go to bed...)