ich777

As far as I can tell this is a card for old analog signals and not for Digital Video Broadcasting, can you still receive analog signals in the area where you live? From what I've found this is a really old card from 2003 or so I think. This plugin isn't designed to support such old cards and doesn't have all the necessary modules built into it for analog TV. DigitalDevices and TBS Open Source drivers won't work for this card, as you said the only drivers that can work are the LibreELEC ones. EDIT: The best thing would be to get a used TBS or something like a DVBSky card that you can get for really cheap prices these days (I also got a DVBSky DVB-C for my development machine for about Euro 35,- and a TBS DVB-S for about Euro 40,- - both are dual tuner cards).

Yes you can do that or you execute every line or at least every command from the script in the terminal.

Eventually but very likely when your appdata and also your docker.img and libvirt.img is on the array. This should not affect the spin down, is the USB device capable of spin down and also does it report that correctly, eventually this is the problem.

This is really strange since I don't experience this issue on my server. @Kris6673 does this also happen on your server?

Erwünscht auf jeden Fall, neuer Thread wäre das beste, bitte evtl. Hidden posten damit sich das vorher nochmal wer ansehen kann und freigibt bzw. dir auch noch Rückmeldung gibt (ich lese OSCAM).

Can you share a screenshot from you Docker template, something must be wrong there, have you changed any ports or something else? Glad to hear that it works now!

Please don't put in Steam credentials if the aren't marked with a red asterisk (*) in the template. You have to enable the console on your game client in Steam and issue the command from the in game console, when you are connected to the server, here is how you do that: Click You have to be also admin on the server, here you can find how you give a user admin rights: Click

Have you enabled the autoupdate within the container? If not please restart the container then it should update (my containers update the game on every start/restart of the container through SteamCMD), mine, with the auto update enabled, did the update about 8 hours ago. Here is the part from the log where it updated: UPDATE CHECK: ---New version of Valheim found, restarting and updating server in 10 seconds--- ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) Update state (0x1) running, progress: 0.00 (0 / 0) Warning: failed to init SDL thread priority manager: SDL not found Update state (0x61) downloading, progress: 98.05 (795715936 / 811503124) Success! App '896660' fully installed. And here a screenshot:

Exactly.

What did you not understand?

No problem here: I can connect and it works without a problem.

Keep in mind that you have go through the build script line by line or at least condition by condition for everything you need.

You can add everything you want to the images, simply enable the 'Custom Build' mode and the container will stop right at the beginning and copy the build script to the specified appdata directory for the container and you can open up a console and do everything step by step and include whatever you want.

The drivers are not compatible with the Quadro 2000 only the Pascal based Quadro P2000. The Quadro 2000 won't work for accelerating your Docker Containers since the nvidia-container-tools needs a card that is from the production branch or from the new feature branch, you can see a full list here: Click (if you click on one of the drivers from the two branches and then click on "SUPPORTED PRODUCTS" you can get a full list what cards are compatible).

Then something is wrong with your configuration since bot use port 27015 and you can't run them at the same time or have you assigned static IP's to the containers?

But not when running Chivalry at the same time or am I wrong? The log looks fine, have you changed anything in the template. I will look into this tomorrow and try to setup the container on my server.

I will look into it ASAP and try to sopve this... Eventually it's a permission problem.

Bitte probier mal einen anderen USB port aus und probier den legacy boot mode aus.

I made this because of a reason. Eventually the mods are causing this, I really can't tell if this is the problem.

Do you got the log open in another window for that container or do you have turned on the advanced view, if so please close the window in the first place or disable the advanced view, this has strictly speaking kothing to do with the container. Keep in mind that this is why the container is marked as beta because I run it through WINE simply because there is no linux dedicated server available and that such a behaviour is expected. This is a browser thing as mentioned above and has nothing to do with the container. Until now I don't get such errors and the server runs just fine, have you changed anything special in the config or the template?

Keep in mind every application is different and every application needs eventually it's own custom "things" so that it will run in a container. So a write up could be really difficult and I have a few containers in the CA App that I try to keep up and running and give support for them.

My PM is basically a full write up for this.

Like the description says, simply restart the container and it should update itself. Also as said above it is not a good idea that a plugin changes another plugin.

As @tjb_altf4 said, the Passed Through switch within UnassignedDevices should solve this "issue", also you should always use this switch wether the disk is passed through to a VM, iSCSI is using this device or something else.

Can you contact @Spectral Force about that? He also has a Discord server for that: https://discord.gg/VwwYA5h Have you eventually set the Validation variable in the container to 'true' if so please leave it empty and try again. EDIT: The file shouldn't be overwritten every time the container is started, have you changed anything in the template? Eventually keep me updated here in the thread what I can change to solve this after you contacted @Spectral Force or joined his Discord about that.