luisalrp

Would be very util to have a community app that notices when there is a new release of a github repo and then builds its container image and uses it on unraid. There are plenty of awesome oss repos where maintainers do not publish images on github or ghcr, but they already have Dockerfiles or docker-compose. It could be a really good feature to use until official images of those repos get published by creators.

Hey, @MyRaid. I got the same problem and solved it changing some rights. Just run this command from apps directory: sudo chown -R 1001:1001 serpbear Best, Luis.

Hey @Collectathon, I can confirm it works with LocalAI. Thanks!

Hey @mickr777, Any plans to do the same for the training repo? https://github.com/invoke-ai/invoke-training Also, you should promote the InvokeAi to a Community App. It is an awesome tools and Image and Template are mature enough. It is really helpful Thanks!

Has anyone managed to get it working using LocalAI? What models in LocalAI and variables in Hoarder? Thanks!

Thanks! It worked!

Hello, I'm getting the following error. I copied the xml from the first post. Maybe the issue is with the //, but I don't know how to fix it. The invokeai folder in unraid has some folders but inside the folders, there are no files. Thanks! Requirement already satisfied: nvidia-nvjitlink-cu12 in /home/invokeuser/.local/lib/python3.10/site-packages (from nvidia-cusolver-cu12==11.4.5.107->torch==2.1.1->xformers==0.0.23) (12.4.99) Requirement already satisfied: MarkupSafe>=2.0 in /home/invokeuser/.local/lib/python3.10/site-packages (from jinja2->torch==2.1.1->xformers==0.0.23) (2.1.5) Requirement already satisfied: mpmath>=0.19 in /home/invokeuser/.local/lib/python3.10/site-packages (from sympy->torch==2.1.1->xformers==0.0.23) (1.3.0) Checking if The Git Repo Has Changed.... fatal: not a git repository (or any parent up to mount point /home/invokeuser) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). fatal: not a git repository (or any parent up to mount point /home/invokeuser) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). fatal: not a git repository (or any parent up to mount point /home/invokeuser) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). fatal: not a git repository (or any parent up to mount point /home/invokeuser) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Local Files Are Up to Date stat: cannot statx '/home/invokeuser//InvokeAI/pyproject.toml': No such file or directory stat: cannot statx '/home/invokeuser//userfiles/models/core/convert/bert-base-uncased/tokenizer.json': No such file or directory Loading InvokeAI WebUI..... start.sh: line 106: cd: /home/invokeuser//InvokeAI/invokeai/frontend/web/: No such file or directory  ERR_PNPM_NO_PKG_MANIFEST  No package.json found in /home/invokeuser/InvokeAI start.sh: line 108: python: command not found

I have the same problem as @SRTG. Since I routed the traffic through binhex-delugevpn, I cant connect anymore to binhex-delugevpn. I selected the bypass local address option in the proxy settings. Any idea?

Hello, I'm trying to run tubesync behind swag, but I'm getting the following error: The config file is pretty simple, but there is something I'm missing: server { listen 443 ssl; listen [::]:443 ssl; server_name ts.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for Authelia include /config/nginx/authelia-server.conf; location / { # enable for Authelia include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app tubesync; set $upstream_port 4848; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Any ideas? Thanks!

A new try: 1. Added to /etc/initramfs -u 9p 9pnet 9pnet_virtio then: sudo update-initramfs -u A net error as a result: root@dappnode:~# systemctl daemon-reload root@dappnode:~# sudo systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# journalctl -xe ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.socket has finished successfully. ░░ ░░ The job identifier is 4040. oct 31 19:31:05 dappnode systemd[1]: Starting Docker Application Container Engine... ░░ Subject: A start job for unit docker.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has begun execution. ░░ ░░ The job identifier is 3950. oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.192037421+01:00" level=info msg="Starting up" oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209365291+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209406349+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209440999+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.209461458+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213446336+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213472759+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213486883+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.213495262+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 19:31:05 dappnode kernel: overlayfs: upper fs needs to support d_type. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support tmpfile. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support RENAME_WHITEOUT. oct 31 19:31:05 dappnode kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. oct 31 19:31:05 dappnode systemd[2107]: var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. oct 31 19:31:05 dappnode systemd[1]: var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit var-lib-mountedDocker-overlay2-check\x2doverlayfs\x2dsupport363317754-merged.mount has successfully entered the 'dead' state. oct 31 19:31:05 dappnode dockerd[7597]: time="2020-10-31T19:31:05.331722926+01:00" level=warning msg="overlay2: the backing <unknown> filesystem is formatted without d_type support, which leads to incorr> oct 31 19:31:06 dappnode dockerd[7597]: failed to start daemon: error while opening volume store metadata database: invalid argument oct 31 19:31:06 dappnode systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit docker.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct 31 19:31:06 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. oct 31 19:31:06 dappnode systemd[1]: Failed to start Docker Application Container Engine. ░░ Subject: A start job for unit docker.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has finished with a failure. ░░ ░░ The job identifier is 3950 and the job result is failed.

To ensure that the mount is performed before docker service init I am adding the following line to /etc/systemd/system/multi-user.target.wants/docker.service in the service section RequiresMountsFor=unraid But I get the following: root@dappnode:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# journalctl -xe ░░ ░░ A start job for unit docker.socket has finished successfully. ░░ ░░ The job identifier is 2309. oct 31 14:44:12 dappnode systemd[1]: Starting Docker Application Container Engine... ░░ Subject: A start job for unit docker.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has begun execution. ░░ ░░ The job identifier is 2219. oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.213669845+01:00" level=info msg="Starting up" oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230913760+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230951468+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230973392+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.230985844+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234123279+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234152959+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234169882+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" mo> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.234181312+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc oct 31 14:44:12 dappnode kernel: overlayfs: upper fs needs to support d_type. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support tmpfile. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support RENAME_WHITEOUT. oct 31 14:44:12 dappnode kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. oct 31 14:44:12 dappnode systemd[4402]: var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. oct 31 14:44:12 dappnode systemd[1]: var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit var-lib-unraidDocker-overlay2-check\x2doverlayfs\x2dsupport666682451-merged.mount has successfully entered the 'dead' state. oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.358626706+01:00" level=warning msg="overlay2: the backing <unknown> filesystem is formatted without d_type support, which leads to incorr> oct 31 14:44:12 dappnode dockerd[8204]: time="2020-10-31T14:44:12.359865909+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2" oct 31 14:44:13 dappnode dockerd[8204]: failed to start daemon: error while opening volume store metadata database: invalid argument oct 31 14:44:13 dappnode systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit docker.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct 31 14:44:13 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit docker.service has entered the 'failed' state with result 'exit-code'. oct 31 14:44:13 dappnode systemd[1]: Failed to start Docker Application Container Engine. ░░ Subject: A start job for unit docker.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit docker.service has finished with a failure. ░░ ░░ The job identifier is 2219 and the job result is failed. lines 3066-3127/3127 (END)

Hello, I am having some issues while trying to run docker inside a Debian VM machine. I need to move the docker data to an unRAID shared volume to take advantage of unRAID capabilities, so I did the following: 1. Stop docker and create the mounting point: root@dappnode:~# systemctl stop docker root@dappnode:~# mkdir /var/lib/mountedDocker root@dappnode:~# cp /var/lib/docker/* /var/lib/mountedDocker/ 2. Edit the /etc/fstab to add the share volume: unraid /var/lib/mountedDocker/ 9p msize=262144,trans=virtio,version=9p2000.L,_netdev,rw 0 0 3. Edit /etc/docker/daemon.json as follows: { "data-root": "/var/lib/mountedDocker" } 4. Mount unraid volume and start docker service: root@dappnode:~# mount unraid root@dappnode:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@dappnode:~# systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-10-30 09:02:43 CET; 1min 20s ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Process: 3980 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 3980 (code=exited, status=1/FAILURE) oct 30 09:02:43 dappnode systemd[1]: Stopped Docker Application Container Engine. oct 30 09:02:43 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:02:43 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:02:43 dappnode systemd[1]: Failed to start Docker Application Container Engine. oct 30 09:03:12 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:03:12 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:03:12 dappnode systemd[1]: Failed to start Docker Application Container Engine. oct 30 09:03:21 dappnode systemd[1]: docker.service: Start request repeated too quickly. oct 30 09:03:21 dappnode systemd[1]: docker.service: Failed with result 'exit-code'. oct 30 09:03:21 dappnode systemd[1]: Failed to start Docker Application Container Engine. What I am doing wrong? Thanks!