Jump to content

erf89

Members
  • Posts

    17
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

erf89's Achievements

Noob

Noob (1/14)

5

Reputation

  1. just tested on beta4 and the dependant containers go into the brief rebuild loop and then are back up and running again after updating the source container of a network!
  2. Ahh, yes sorry my misunderstanding! Thanks for clarifying and also for finding the fix
  3. Ahh okay - I guess this feature in beta3 is just replicating using Network: None and the extra --network command anyway... that always worked previously, updating the container with dependencies did always send those dependant containers into a "rebuilding" spin but it only ever lasted a few seconds and then it was all good again So in beta4, will the feature be gone (and I go back to using network: none and the extra arg.), or will it be fixed so that the containers can still update?
  4. sorry just trying to catch up on all these posts. I have a custom docker network setup just for the sole purpose of referencing containers by their names - all my containers use this network, bar the 3 containers using another container as their network. My Gluetun container is then used as the network for the tailscale docker container (to create an exit node in tailscale). Pre-beta3 I was just using 'Network: None' and then had the extra arg of --network=container:gluetun but since beta3 I wanted to try the new functionality, so I used the Network: Container, Container: Gluetun... Getting the docker run for my gluetun is a nightmare because I can't run it without changing the dependant containers, but it's just the stock gluetun CA template with my variables in, and network set as custom (my one custom network for all containers): Docker Run for Tailscale with the Network Type set as Container docker run -d --name='tailscale-gluetun' --net='container:gluetun-uk' --pids-limit 2048 -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="farrosphere" -e HOST_CONTAINERNAME="tailscale-gluetun" -e 'TS_HOSTNAME'='vpn-uk' -e 'TS_AUTHKEY'='' -e 'TS_AUTH_ONCE'='true' -e 'TS_USERSPACE'='true' -e 'TS_ACCEPT_DNS'='false' -e 'TS_EXTRA_ARGS'='--advertise-exit-node --accept-routes' -e 'TS_STATE_DIR'='/state' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/dkaser/unraid-tailscale/main/logo.png' -v '/mnt/user/appdata/tailscale-gluetun-uk':'/state':'rw' 'tailscale/tailscale:stable' 741733a0ede2f6865b522c15648a18ccdd84c0c79143931a952d17c3594c6ef9 Docker Network List: NETWORK ID NAME DRIVER SCOPE e9e1d1fbdc8a br0 ipvlan local 1238e44c05f3 bridge bridge local 60956d51ed99 farrosphere bridge local e0b0892b2eb4 host host local 72de74c4c178 none null local
  5. Using the new docker container network feature, and I'm unable to update a "source" container whilst a container that uses it as a network exists - whether that container is running or stopped. Looks like I would have to go into the container using the network, set it as none/something else, to update the source container, and then go back in and change back to using the container as a network. Any slicker way for Unraid to do this in the background?
  6. Anyone having problems adding/remove tiles from the Dashboard using Tile Management? It's just blank for me: If I clear my cookies I get the default Dashboard back and all the tiles which I can re-order/remove, but can never then add them back later.
  7. Saved me from rolling back/pulling my hair out! Thanks! 😄
  8. I have the CA Mover Tuning plugin installed and setup to run at 85% full - was working no issue until today, I've updated to Unraid 7 beta, and now I can't get it work, and I also can't get manual mover to work either (I set "Move Now button follows plug-in filters" to No), also tried using the Move Now button inside the Share settings page, also no luck! Snip of syslog below, happy to provide any other diagnostics detail! Jul 8 00:55:21 emhttpd: shcmd (170): /usr/local/sbin/mover start |& logger -t move & Jul 8 00:55:21 root: Starting Mover Jul 8 00:55:21 root: Forcing turbo write on Jul 8 00:55:21 kernel: mdcmd (43): set md_write_method 1 Jul 8 00:55:21 kernel: Jul 8 00:55:21 root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 0 0 0 '' '' '' '' '' '' '' '' 50 Jul 8 00:55:21 move: Log Level: 1 Jul 8 00:55:21 move: /usr/local/sbin/move does not exists, creating soft link Jul 8 00:55:21 move: ln: failed to create symbolic link '/usr/local/sbin/move': File exists Jul 8 00:55:21 move: mover: started Jul 8 00:55:27 move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 206: /usr/local/sbin/move: No such file or directory Jul 8 00:55:27 move: cat: write error: Broken pipe Jul 8 00:55:27 move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 119: /usr/local/sbin/move: No such file or directory ### [PREVIOUS LINE REPEATED 4 TIMES] ### Jul 8 00:55:27 move: mover: finished Jul 8 00:55:27 root: Restoring original turbo write mode Jul 8 00:55:27 kernel: mdcmd (44): set md_write_method auto I should add that as well as being on Unraid 7 as of today, a few days ago I also changed my cache pool to zfs from btrfs, however the Mover getting everything back onto the Cache at that point worked fine, and today is the first day I'm hitting my 85% again.
  9. Just installed steam-headless but can't get it to work - WebUI gives me the noVNC screen but when I click Connect, I get "failed to connect to server". I have a Radeon 6400 and have installed Radeon-TOP, and can see the GPU on my Dashboard. (GPU was previously bound and passed through to a VM, I have unbound and rebooted unraid to get it back to normal and see the GPU on my Dashboard). The first time I installed steam-headless, I ran it with --device=/dev/dri in the extra parameters to use my Intel iGPU, however because I only want it to use the Radeon GPU I have removed that, no joy, and then completely uninstalled, removed appdata folder and reinstalled without ever adding /dev/dri, and still the same issue, can't get it working. In the logs I can see the below: [ /etc/cont-init.d/60-configure_gpu_driver.sh: executing... ] **** Found Intel device 'Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)' **** - Mesa has already been installed into this container **** Found AMD device '03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c7)' **** and then I get a load of WARN: exited entries in the logs Anyone able to help?
  10. Fix for now is to rollback to the previous version: binhex/arch-delugevpn:2.1.1-6-03
  11. For anyone attempting to install Cryptpad needing to use different ports (3000 is used by Grafana by default which a lot of us will already have installed!), I struggled at first but wanted to share how I eventually got it working! Decide ahead of time which ports you want to use (I went 5000, 5001, 5003) as this will speed up the setup process. I followed the instructions in CA Apps to change permissions, make directories etc., then installed the container, but amended the pre-set Ports. You will need to REMOVE Port 1, Port 2, Port 3; and then re-add them, matching the Container Port to whatever Ports you intend to use (so Port 1 should show 5000 in each box) Install the Container, and then we can finish with the amends to config.js. Amended the config.js file as per instructions, ensuring you Uncomment the httpAddress setting and set as 0.0.0.0 I then uncommented and amended the three pre-set ports (3000, 3001, 3003) to be 5000, 5001, 5003. After all this I then was able to get into Cryptpad WebGUI successfully and create docs.
  12. Ahh yes, that's working now! Thanks for your help!
  13. Thanks for the quick response! Just did a force update but still not working, the Logs are very much the same though, says it's started the metrics server
×
×
  • Create New...