frakman1

I love that it can be a NAS, VM manager and Docker manager all at once. I wish there was a free tier like most other services (and from what I've been told, the way it was before). Just a one or two drive solution for people that can't afford the license.

I tried to install this from the APP store (binhex-preclear) but I got this error while running the docker run command:

In their infinite wisdom, the creators of this app made the password field be the md5 hash of your actual password. See my earlier post here for details on how to set it.

I just updated mine to the latest 12.5.2 and it works fine: I've noticed that on some docker containers that keep crashing sometimes, that if I edit the Docker configuration and just add an empty field or make a trivial change to the description and Apply it, then it re-runs the docker command to create the container and it starts working again. Even with a pinned version of the image so it can't be because of a new feature or bug-fix. Try doing that.

In my screenshot above I show the string I used for "Repository". This allows you to select the tagged versionof Gitlab that you want. Change it from: gitlab/gitlab-ce:latest to : gitlab/gitlab-ce:12.5.2-ce.0 (or anything you want) You can go to dockerhub and choose from a list of official tags.

@ElectricBadger @JasterCan you go back to a working earlier version? I have mine pinned to 12.5.2-ce.0 which I know works for me. I don't update the docker but when I do, I pin it to the version I want. See screenshot below for my Docker Settings

Oh sorry for the misunderstanding. What version of Gitlab is it? I'll try upgrading mine to the latest and test it out.

I have mine up and running. There's a bunch of configuration you have to do to get it to work with Gitlab. This is a good start https://docs.gitlab.com/ee/integration/sourcegraph.html#enable-the-sourcegraph-feature-flag It's a bit tricky with a lot of configurations. Let me know if you run into problems and I'll be happy to show you what I did.

@kimocal @bnevets27 I'm having an issue whereby the Prime OS VM I installed has a memory leak. Even the vanilla, fresh installation with nothing else. I confirmed it using "watch free -m" at the shell (Alt+F1, then Alt+F7 to get back to UI) and saw the "free" column gradually go down. The VM would eventually seize up and become unusable. I tried both the Standard and Mainline 0.4.5. I used the same VM settings as everyone else seems to. I even tried both Machine types (Q35-3.1 and i440fx-3.1). See attached VM settings and Kernel version screenshots below. Has anyone run into this or can confirm my results?

For those of you (like me) who were excited about the announcement that Gitlab now integrates with Sourcegraph, I created a Sourcegraph Unraid template based on this Gitlab template. You can find it in Community Applications under "Sourcegraph". It's my first contribution so please give it a shot and let me know if it works for you or not. If you want to know more about Sourcegraph, this is a quick screencast I had to enable the feature at the Gitlab rails console using this: gitlab-rails console Feature.enable(:sourcegraph)

Thank you! That was it. I was looking all over for it *inside* the docker container.

I'm using the Gitlab CE docker. For some reason, it thinks that it's URL is http://unraid:9080. This impacts all related services and links. Nothing on my home network knows what unraid is so nothing works. Where do I change it?

@rwarren873 This tripped me up too. The password field in the docker template is actually an md5 hash of your password. To get that, run this on any Linux terminal: echo -n mysupersecretpassword | openssl md5 (stdin)= 117a520adbd19eff51100215aa7a7fbf That value (117a520adbd19eff51100215aa7a7fbf) is your password hash. Put that in the password field of your docker template, and use the actual password (mysupersecretpassword) when you login to Guacamole. I found this information on the docker info page in dockerhub: https://hub.docker.com/r/linuxserver/calibre

Well, you used the word 'plugin' so I did just that and looked for it in the plugins tab. Ok. I installed it, but what am I supposed to select to "Auto Update" in order to patch the OS and fix the DockerHub issue? This particular Calibre docker container under Settings->Docker Auto Update Settings ?

Can you please share where this auto-update plugin is located please? I don't have it installed and I need a URL to add it.

Is there a way to automate or schedule the launching and closing of VMs? I have some web automation operations that I want to run in a cron job on a VM but I don't want the VM to be up all the time. I'd like to be able to start a VM at a scheduled time and then turn it off at another scheduled time periodically. Is there an API to starting and stopping VMs? On the topic of VMs. Is it safe to "Stop" a Linux Ubuntu VM from the Unraid VM tab without actually shutting it down within the VM? Or does the "Stop" operation take care of telling the VM to shut down gracefully. I don't want to just pull-the-plug on a VM if I don't have to.

Mine just has these three ports: 9080, 9443, 9022 by default.

Calibre can only see the host folder that you mapped in the docker template using the "Library Location" parameter. Open your docker template page for Calibre and change the Library Location to /mnt/user/Downloads/calibre and restart the container. Calibre should then be able to access this folder via its /books folder.

Perhaps it's not a bug with the container but since this is an Unraid forum and this is a topic about supporting the linuxserver/calibre container, I am bringing it up here. My host's TZ is correctly set to Eastern Time zone. # date Thu Oct 3 11:41:45 EDT 2019 # clock 2019-10-03 11:42:33.310583-04:00 # date +"%Z %z" EDT -0400 However, when I update the container, the docker run command is using Los Angeles TZ: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='calibre' --net='proxynet' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'GUAC_USER'='xxx' -e 'GUAC_PASS'='xxx' -e 'PUID'='99' -e 'PGID'='100' -p '8080:8080/tcp' -p '8081:8081/tcp' -v '/mnt/user/myData/media/ebooks':'/books':'rw' -v '/mnt/user/myData/media/ebooks/imports':'/import':'rw' -v '/mnt/user/appdata/calibre':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'linuxserver/calibre' I didn't add an extra TZ parameter so I don't know where it is getting it from. See Template view below:

Kindly explain how this is not a bug. There is a TZ field in the template. I fill out the TZ field. The field is ignored and reverts to the host TZ. That sounds like bug in my book.

The TZ should not come from unraid. It's an input parameter to the container which should be honored. If it's coming from Unraid then that's a bug that should either be fixed or have the TZ field removed if it isn't doing anything.

@saarg Here you go: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='calibre' --net='proxynet' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'GUAC_USER'='<redacted>' -e 'GUAC_PASS'='<redacted>' -e 'PUID'='99' -e 'PGID'='100' -p '8080:8080/tcp' -p '8081:8081/tcp' -v '/mnt/user/myData/media/ebooks':'/books':'rw' -v '/mnt/user/myData/media/ebooks/imports':'/import':'rw' -v '/mnt/user/appdata/calibre':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'linuxserver/calibre' Note the wrong TZ variable despite it being set in the template:

@Stupifier Can you share with us what you did to get it to work? Do you have to first mount the usb drive in the Main page, then use /dev/sdX?

I noticed that when I changed the TZ to America/New_York, it still uses the default America/Los_Angeles. Some template values don't seem to make it into the docker run command for some reason. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole' --net='br0' --ip='192.168.86.2' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TCP_PORT_53'='53' -e 'UDP_PORT_53'='53' -e 'TCP_PORT_80'='80' -e 'PUID'='99' -e 'PGID'='100' -e 'ServerIP'='192.168.86.2' -e 'ServerIPv6'='' -e 'DNS1'='9.9.9.9' -e 'DNS2'='149.112.112.112' -e 'IPv6'='False' -e 'TZ'='America/New_York' -e 'WEBPASSWORD'='admin' -e 'INTERFACE'='br0' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/user/appdata/pihole/pihole/':'/etc/pihole/':'rw' -v '/mnt/user/appdata/pihole/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --dns 127.0.0.1 --dns 1.1.1.1 --restart=unless-stopped 'pihole/pihole:4.3.1-4_amd64' WARNING: Localhost DNS setting (--dns=127.0.0.1) may fail in containers.

I was quoting somebody else's "docker run". Mine is default 8080:8080 and 8081:8081 Ultimately, it doesn't matter because I click on the "WebUI" menu item which opens to "http://192.168.86.98:8080/#/" and get this: Anyway, thank you for the tip for getting a "docker run". It seems like I do have to make a trivial change, update and change it back just to see the docker-run syntax which seems a little silly. It would be nice if the UI included the last syntax it used for "docker run" in an unused text field especially if that command is important for troubleshooting purposes. By the way, how come I don't see the "docker run" command when I look at the Unraid server's logs?