alexciurea

Hi @AinzOolGown In my case I faced a problem with my gitlab-ce docker installation during updates because: 1) no autoapdates, and 2) I did not follow the update path recommended by gitlab. When I manually updated, it jumped from a very old version to latest. The container was not starting because db was failing; I think the db upgrade scrips failed. So I manually updated step by step, using specifically the respective tags in the docker, based on this info below: https://docs.gitlab.com/ee/update/#upgrade-paths This resolved the issue. Maybe this is already common knowledge for many, but I hope it helps someone failing like me... -a

hello seems that fix common problems plugin report the gitlab-ce ports as non-standard. Getting in FCP errors like: Docker Application GitLab-CE, Container Port 22 not found or changed on installed application Docker Application GitLab-CE, Container Port 80 not found or changed on installed application Docker Application GitLab-CE, Container Port 443 not found or changed on installed application somebody else reporting this in the GL-CE docker support thread. i guess we can ignore, but probably the plugin reporting such error should be corrected?

same issue here. I don't remember if i changed these to other values. tried to change to 22, 80 and 443, but container does not start anymore. tried to remove the container and reinstalled, but same values are used by default (9022, 9080, 9443). will post also in the fix common problems plugin

+ 1 for the compose / kubernetes in unraid out-of-box (and also using multiple unraid nodes)

in this situation, ideally, you should be able to passthrough your 980 without specifying the rom good luck!

sure if you see the GPU in the VM definition listed for passthrough, it does not mean that it will work if it's the only GPU in your system (something that you didn't clarify), it will not work (give video output) unless you use the rom trick (this is relevant for NVIDIA; AMD i heard deos not have this issue, but i cannot personally confirm)

@zerrikan unraid uses 1 GPU for displaying the console output usually, that's the integrated GPU. Or in case of platforms without integrated GPU, unraid will use the GPU in the first pcie slot (a.k.a primary). This guide refers to passing through an NVIDIA primary GPU. Basically telling unraid to give up using that GPU for console, but to use it as passthrough in a VM. A rom file will be required in order for the procedure to work. As of today, one cannot passthrough an NVIDIA primary GPU without doing the steps in this guide. to comment on your specific confusion, i assume you have 2 GPU's in your system (Integrated + 210). Passing the non primary GPU 210 to a VM will be easier and might not require the steps in the guide.

thanks gridrunner @KRSogaard - my understanding is that you will use the integrated gpu for unraid and gt610 should passthrough regularly, without the steps mentioned by gridrunner. gridrunner's instructions are required when no GPU can be allocated to unraid.

hello Is there performace loss when playing the game in the vm with the gtx1070 passthrough? possible to share some benchmark comparison, between native Windows 10 OS and W10 in VM, on same number of CPU cores allocated? thanks