nox969
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by nox969
-
-
Hi binheh,
nice job on this one. I am running into a small issues with remote repo connections as I keep getting "stderr: Could not create directory '/.ssh' when setting up source code management portion of a job. " in any configuration. I'm sure it's a small issue but as I don't have time to investigate today, I thought I would ask if you know of the top of your head.
Thanks
-
RDP-Calibre Update:
Due to popular demand, I am adding a couple of new features, both of which are only for advanced docker users. Regular users need not worry about them, when they update, nothing will change for them. Below are the steps to enable these features:
Custom Library Location:
1) First add a new mount point for the library location. Example: /path/to/library (host), /library (container)
2) Open the advanced view and add a new environment variable. Example: Name= LIBRARYINTERNALPATH Value= /library
3) When you fire up calibre the first time select your library location. Example: /library (If updating, change the location in settings)
Url Prefix for reverse proxy
1) Open the advanced view and add a new environment variable. Example: Name= URLPREFIX Value= /calibre
2) To access the webserver, go to http://SERVERIP:YYYY/calibre
I'm running into an issue with the custom library location on unraid 6.2 / latest RDP-Calibre. When trying to select the new library location (as per point 3) the "Next" is disabled (this only happens with the custom mount, if I select the /config I can proceed as normal.).
If, on the other hand, I try to do this after the initial setup (by changing the library location) I get the Read-only filesystem errors regardless of the actual folder permissions.
Does anybody have ay insight into this?
Thanks
You need to change it in the calibre gui, not the unraid gui. After you start the container the first time, open its webgui and it will ask you where to store the library
Thanks aptalca,
actually the issue appeared to be the use of "library" as a term. Once I switched to using a differently named variable and internal path value it worked as expected.
-
A small issue I've run into is that the viewing function will fail due to a missing Zlib. Specifically, the error is:
clsTbsZip ERROR with the zip archive: Unable to uncompress file "META-INF/container.xml" because extension Zlib is not installed.
Now, installing this is trivial within the container, but it would be great if the fix is included in the docker build itself.
-
RDP-Calibre Update:
Due to popular demand, I am adding a couple of new features, both of which are only for advanced docker users. Regular users need not worry about them, when they update, nothing will change for them. Below are the steps to enable these features:
Custom Library Location:
1) First add a new mount point for the library location. Example: /path/to/library (host), /library (container)
2) Open the advanced view and add a new environment variable. Example: Name= LIBRARYINTERNALPATH Value= /library
3) When you fire up calibre the first time select your library location. Example: /library (If updating, change the location in settings)
Url Prefix for reverse proxy
1) Open the advanced view and add a new environment variable. Example: Name= URLPREFIX Value= /calibre
2) To access the webserver, go to http://SERVERIP:YYYY/calibre
I'm running into an issue with the custom library location on unraid 6.2 / latest RDP-Calibre. When trying to select the new library location (as per point 3) the "Next" is disabled (this only happens with the custom mount, if I select the /config I can proceed as normal.).
If, on the other hand, I try to do this after the initial setup (by changing the library location) I get the Read-only filesystem errors regardless of the actual folder permissions.
Does anybody have ay insight into this?
Thanks
-
Hi!
I have been using plex for more than a year now.
I noticed in my routers logs blocking access for a few android devices with plex app installed trying to connect to a bogon IP address. I found this address also in Plex docker.
Does anyone have any idea what is going on?
The weird thing is that the android devices are looking for 172.17.0.1 outside my lan in the internet.
I googled before posting and the only think related (I think) is this
https://github.com/timhaak/docker-plex/issues/54
09:19:19 firewall,info drop 172 forward: in:bridge-local out:pppoe-out1, src-mac xxxxxxx, proto TCP (SYN), 192.168.1.63:39411->172.17.0.1:32400, len 6 0
ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[274]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 6 3000 /config/Library/Application Support d Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.2. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. [b]Registering new address record for 172.17.0.1 on docker0.IPv4.[/b] Registering new address record for 192.168.1.2 on br0.IPv4. Server startup complete. Host name is TOWER.local. Local service cookie is 1897350774.
I can confirm that I'm seeing the same. An interface configuration for mDNS group on 172.17.0.1 during the startup and subsequent calls to the 172.* range when using the local web (browser) interface.
Now this could also be the reason behind the local web interface being perceivable slower than when accessing via plex.tv.
I'll try to do a further analysis this weekend but does anybody have any ideas?
[Support] binhex - Jenkins
in Docker Containers
Posted
Hey binhex, ignore my question. It was most likely mistake on my part. Readding SSH credentials solved all connectivity issues.