bucky2076

Members
  • Posts

    40
  • Joined

  • Last visited

About bucky2076

  • Birthday December 13

Recent Profile Visitors

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

bucky2076's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. good luck with it.. Bear in mind, I got very uneven results, until such time I put an HDMI dongle on the graphics card hdmi port. After that its been smooth sailing. Also does not hurt to dump the bios to ensure the card is working with original bios. I could never get a consistant result trying to use one of the techz bios downloads. Good luck with it. /ben
  2. you can go back quite easily to the previous version, as I did. If you read above you will see there is a workaround due to a breaking change.
  3. ok, I got it working. Took weeks of effort... and has been a rough journey. If it helps someone else... here is what seemed to work for me.... My environment Swapped over the unraid 6.9 rc2. Seems quite stable now. Nice handling of vfio. onboard video (intel) used for unraid (set as primary in bios) MSI GTX 1050 ti oc - Nice card but very finicky. Tried Manjaro KDE/Gnome Win10, PopOs, Ubuntu Gnome - either got black screen or LLVMpipe for video. Tried a bunch of vbios available from techpowerup. Tried dumping my own bios from unraid as per spaceinvader Solution I downloaded HirenBootCD, took out the unraid usb key and started the server with Hiren. It come up in Windows PE tweak your bios and ensure gtx 1050 is set as primary. Attach monitor too... run GPU-Z (included in Hiren), and dump the vbios. Strip out the header of the vbios using a python program or hex editor as per spaceinvader Attach physical monitor to the gtx hdmi, and fire up your vm from another machine (desktop) I use nomachine as remoting software. so remote to the vm and worked great on ALL of the above VM's todo: Substitute an HDMI dummy plug instead of physical monitor.
  4. With respect to ports... good to be able to see in the template which ports are operational if you are a beginner. I found that useful. To be honest, I had a conflict with my unifi controller and had to massage one of the ports. For MQTT... I am actually running home assistant in a VM at the moment. The VM manages the HA software and an MQTT broker, which I find very convenient. That was the basis of my request... but another container seems appropriate. Open Hab looked more mature to me than HA... I'm still at the beginning of the journey, so can afford to poke around the different offerings. Thanks for doing this by the way.
  5. suggestions: for openhab 3. If you are going to be making changes to this template... can I suggest you a few enhancements ? take the "2" out of the mount file names expose used ports so they can be overriden (8080 conflicted with my unifi controller) option to include an MQTT broker in the same container (stretch) just my 2 cents
  6. I just installed the most recent 6.9 RC. I am wrestling with Nvidia GPU passthrough. I tried to set my vm back to use vnc and then launched, but got the following error on the NoVNC screen. >> noVNC encountered an error: SyntaxError: import not found: hasScrollbarGutter http://buckyu.local/plugins/dynamix.vm.manager/novnc/app/ui.js?ts=20200718:11:34 >> This is a showstopper. Not even sure which dynamix plugin this refers to: Rolling back to 6.8.3 in the meantime. >> update: This is a firefox problem. Works fine in chrome. >>>
  7. yeah me too... can't get popos to avoid the black screen when switching to nvidia card.
  8. bucky2076

    Jitsi?

    hi johnathan, your comment gave me reason to continue some investigation. After doing a bit more tinkering.... The jitsi VM is an ubuntu server vm, located on the same unraid server as the docker containers. Unraid networking was not able to route internally between the VM and the docker LE bridge network. That was a showstopper for me unfortunately, so licking my wounds and retreating for the moment. As a temporary measure, I am using custom external ports for jitsi, (81:444), and directing the router to forward directly to the VM without using LE as the gateway. many thanks, bucky2076
  9. bucky2076

    Jitsi?

    I tinkered with this quite a bit, and have some observations worth mentioning. The use of Docker-Compose/Portainer, alongside native unraid docker (Dockerman) handling, is certainly interesting, but fraught with problems in my opinion. These two are competing technologies that do not work well together. It clutters things up, and is responsible for ongoing errors warnings. So you have a few options to consider. Move all your dockers to compose/portainer. - Unraid support for compose is limited. If you want to maximise your use of unraid, just live with it the way it is. Move jitsi to a VM. Containers are for microservices, and is not meant for every use case out there. There are a couple of youtubes (crosstalk solutions) that take you through the steps. I would love to get this working while keeping letencrypt nginx proxy docker acting as a front end. Would be cool. Hybrid solution is to create a vm, and run docker in the vm, and then set up portainer/lxc as an alternative to dockerman. Run jitsi dockers here, or migrate all your dockers. You are going through an extra layer of virtualisation... so not sure how much this would drain performance. I ran up an instance of ubuntu server, and just going through the typical hardening process for a server. Lots to learn and fun doing this. Install of jitsi is a simple apt command once you get past server hardening. I am playing with all these possibilities, and honestly don't have a conclusion at this time. Strengths and weaknesses for all options
  10. fair enough. I've capitulated and bound my new license to a normal quality usb stick. Giving up on the small unltrafit 3.1, as I don't want to invite trouble.
  11. i also bought the ultrafit 3.1, and was dissapointed to see the automatic method would not work for this unit. I might try the manual install... is it documented ?
  12. saarg, the basic unraid template did not work for me, and I had to tear my hair out. DB_USER variable was incorrect. Needed to be DB_USERNAME Same issue for DB_PASS Passing IP/Port did not work for me on the DB_HOST /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='bookstack' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'DB_HOST'='192.168.92.254' -e 'DB_USERNAME'='ben' -e 'DB_PASSWORD'='xyz' -e 'DB_DATABASE'='bookstack' -e 'APP_URL'='' -e 'PUID'='99' -e 'PGID'='100' -e 'DB_PORT'='3306' -p '8083:80/tcp' -v '/mnt/user/appdata/bookstack':'/config':'rw' 'linuxserver/bookstack' I've moved on now, experimenting with Traefik for reverse proxy.
  13. simply the template variables are misleading, causing some confusion. Also, the port assignment did not work when adding port to host name., I had to break this out to its on env var. The .env provides the proper name for these variables.
  14. oh thanks I did not realise that about unraid docker.... I have done some docker stuff in a normal linux host, and the docker networking is quite sophisticated. You would simply use the name of the docker rather than its internal IP. You also have the opportunity to manage your own networking so that you can split your backend from your foreground tasks across different network subnets (sql database, versus web server hosts). I did obscure a few things in the above post for obvious reasons... Name/PW and such. My server IP internally is actually 192.168.92.254, so there you go. I am ok using the host IP since that dosen't change. The 172.xx.xx.x.. ip changes each time you present a different order during startup. I did leave a message on bookstack issues section (git) suggesting the parameters need some attention. Thanks again for the chat... hopefully this will help the next newbie... /bucky2076
  15. mariadb... /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='mariadb' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'MYSQL_ROOT_PASSWORD'='XYZ' -p '3306:3306/tcp' -v '/mnt/user/appdata/mariadb':'/config':'rw' 'linuxserver/mariadb' bookstack.... /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='bookstack' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'DB_HOST'='192.168.xx.254' -e 'DB_USERNAME'='abc' -e 'DB_PASSWORD'='XYZ' -e 'DB_DATABASE'='bookstack' -e 'APP_URL'='' -e 'PUID'='99' -e 'PGID'='100' -e 'DB_PORT'='3306' -p '8083:80/tcp' -v '/mnt/user/appdata/bookstack':'/config':'rw' 'linuxserver/bookstack' and finally .env DB_HOST=172.17.0.3 DB_PORT=5506 DB_DATABASE=stack DB_USERNAME=n DB_PASSWORD=me This config actually works... because of the following: .env is ignored if overidden with params... DB_USER in template replaced with USERNAME DB_PASS changed to PASSWORD DB_PORT was added Would be better if it accepted the host as the container name rather than the ip.