Oh nevermind, the build number is:
linuxserver/radarr:arm32v7-version-v0.2.0.1504
This works, but it borked my radarr configuration and I have to re-configure everything.
Oh nevermind, the build number is:
linuxserver/radarr:arm32v7-version-v0.2.0.1504
This works, but it borked my radarr configuration and I have to re-configure everything.
Display MoreHi everyone, I am writing because I encountered some errors while updating the docker container for Radarr, maintained by linuxserver.
They issued an update last night :
following the link ( https://docs.linuxserver.io/fa…ges-based-on-ubuntu-focal ) their advice is:
So far, I have managed to run the previous-last image using the following tag: linuxserver/radarr:version-v0.2.0.1504
But my question is: is this safe to execute these command on a raspbian lite image on which OMV5 run?
I have the same problem with radarr too on my raspberry pi. I tried running that radarr version 1504 but I couldn't find it. Itried to backtrack to the libseccomp2 core and it doesn't work either. I tried putting an older version of radarr up to about 15 days ago and it doesn't work either. Anybody konw how to fix this?
I get slow transfer speed if I have too many torrents running or any software that you are using the hard drive, IE I use emby. I never used deluge, but I use haugene/transmission-openvpn:latest-armhf docker which is good for openvpn and transmission.
FYI, I am using the raspberry pi 4 4gb, with a 5tb seagate hard drive.
This happened to my Raspberry pi running OMV where my sd card got corrupted or something. At first I can't go to the OMV console and I have to constantly reboot my raspberry pi 4 to get it up and running. Fortunately, when I set up my raspberry pi, I used dd to backup my sd card and then used pi shrink. I was lucky enough to get a shrunk img file from a backup and copied it to my computer.
I originally installed an 16gb sd card from Microcenter shrink to about 3.7gb img file. Then I figured that I used a "reliable" 8gb samsung sd card to dump the image and then used the raspi-config tool to expand it. It is a good thing when I moved all the dockers into the hard drive instead of the sd card otherwise it will be more of a pain
You can secure the website using a login, password to access the webpage.
You should also install LetsEncrypt docker (which includes nginx web server) and use a reverse proxy subfolder to do access to your website. That way, you can access your website via https://<yoursite>duckdns.org/transmission/web/
Hi,
I am running raspberry pi 4 using Openmediavault to backup my sd card and shrink the file via pishrink. So every Tuesday at 4am, I run the scheduled tasks command under root:
sudo dd if=/dev/mmcblk0 of=/sharedfolders/Appdata/sdbackup/backup.img bs=1M
This job runs without issues.
At Tuesday 5am, I ran a job to shrink this file
sudo pishrink.sh /sharedfolders/Appdata/sdbackup/backup.img
and it would not run.
When I ran the pishrink command manually in the scheduled tasks panel, it would run fine. Is there a reason why this is happening? Thanks.
You might as well install Letsencrypt docker because this includes nginx.
It should be located in /srv/dev-disk-by-label-data/appdata/letsencrypt/etc/letsencrypt/live/mysite.duckdns.org/ (assuming that mysite.duckdns.org is your registered site by letsencrypt.)
Agreed. For mariadb, you can map ports: 3306:3306. Letsencrypt is the web server ported outside and should own 443 and 80. For me, I would map something like 2443:443 and 2080:80. Have your router route ports 443:2443 and 80:2080 respectively. That way, you can still use your OMV port server at port 80.
For nextcloud, you can map something like 3443:443 and 3080:443.
What is the URL that you are using for nextcloud? It looks like you are only registering www as a subdomain. If you are trying to register ohiskyy.duckdns.org as the main nextcloud subdomain, it don't think that would work. I could never get nextcloud to work as a subfolder. I would also register nextcloud as a subdomain in letsencrypt and configure nextcloud.ohiskyy.duckdns.org as your nextcloud site.
You didn't specify DNS Servers in OMV. Go to System -> Network -> Interfaces, on your eth0 interface, go all the way down and put your dns server under the advanced settings.
Before doing this, you might want to put a delay to startup your docker by 30 seconds.
https://forum.openmediavault.o…V5-Pi4-This-might-fix-it/
Afterwards, you can move your contents to your usb drive. I created a share and dump the data into /sharedfolders/<your shared folder name>/docker
https://www.guguweb.com/2019/0…other-location-on-ubuntu/
I followed these instructions here. However, before this, you might want to go to OMV portal, go to System -> OMV-Extras, remove /var/lib/docker in "Docker Storage" so it will reference the /etc/docker/daemon.json file.
Your nextcloud.subdomain.conf file is located in letsencrypt docker's configs, not in nextcloud.
/srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs
Display MoreTrying to set up Popcorn hour transformer on OMV4 (rock64)
Keep getting
What am I doing wrong?
My config:
Display MoreBash
- /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted- /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data #/srv/dev-disk-by-label-disk1 needs to be adjusted- /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
There's nothing wrong with your nextcloud docker. Rather with your nextcloud.subfolder.conf file. Change the "proxy_max_temp_file_size from 2048m to 1024m. That's what's worked for me.
Display MoreTrying to set up Popcorn hour transformer on OMV4 (rock64)
Keep getting
What am I doing wrong?
My config:
Display MoreBash
- /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted- /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data #/srv/dev-disk-by-label-disk1 needs to be adjusted- /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
There's nothing wrong with your nextcloud docker. Rather with your nextcloud.subfolder.conf file. Change the "proxy_max_temp_file_size from 2048m to 1024m. That's what's worked for me.
I never used plex server so I can't tell you how it generates its metadata, but I supposed that it is similar to emby. Like I said, install radarr and jackett dockers and manually import those files and it will generate the metadata for you.
I have a similar issue with emby where the metadata is not downloading and it is probably due to me how I name my files and emby would not recognize them. IE. if you have your movie like yourmovienamehere.mp4, it would not work because there are no space or period between the words. I ended up installing radarr, add the movie, click on "wanted" sign, and do a manual import of the movies folder and then radarr will put the metadata back to emby. There's a whole process of installing linuxserver/radarr:arm32v7-latest, linuxserver/jackett:arm32v7-latest and getting to work with plex. You can watch techno dad life in youtube on how to get this configured.
Which images?
I mean arm64v8 dockers.
In the last few months, Rasbian Buster gives you the option to boot up to a 64 bit kernel instead of a 32 bit. I am curious of the current support of 64 bit running ARM and after the kernel is upgraded can you use arm64v8 images? Thanks.