nVitius

Oh, you're right. I couldn't seem to connect to the serve, so I figured it just wasn't running. The connection doesn't seem to be working from either the local network or outside. I have port forwarding set up and I have tried with both Bridge and Host network modes on the container. Aside from trying that, I haven't changed anything in the Docker config. I can't connect to any of the ports with telnet. EDIT - I also tried giving the container a static IP. Confirmed it is showing up as a client on my router with the correct status IP. Server seems to still not be listening on any of the ports.

Has anyone had success running this for "The Forest"? I'm getting this error in the logs right now: EntryPointNotFoundException: AttachConsole at (wrapper managed-to-native) Bolt.ConsoleWriter/PInvoke:AttachConsole (uint) at Bolt.ConsoleWriter.Open () [0x00000] in <filename unknown>:0 at CoopDedicatedBootstrap.ServerRoutine (System.String[] args) [0x00000] in <filename unknown>:0 at CoopDedicatedBootstrap.Awake () [0x00000] in <filename unknown>:0 Earlier in the logs, I am also seeing these errors: GfxDevice: creating device client; threaded=0 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:d3d:wined3d_adapter_find_polyoffset_scale PolygonOffset scale factor detection failed, using fallback value 2^23. 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:d3d:wined3d_adapter_find_polyoffset_scale PolygonOffset scale factor detection failed, using fallback value 2^23. 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1) 0009:err:d3d:wined3d_adapter_find_polyoffset_scale PolygonOffset scale factor detection failed, using fallback value 2^23. Direct3D: Version: Direct3D 11.0 [level 10.1] Renderer: NVIDIA GeForce 8800 GTX (ID=0x191) Vendor: NVIDIA VRAM: 15714 MB Driver: 1.0 D3D shader create error for vertex shader [0x80070057] D3D shader create error for pixel shader [0x80070057] D3D shader create error for vertex shader [0x80070057] D3D shader create error for pixel shader [0x80070057] D3D shader create error for vertex shader [0x80070057] D3D shader create error for pixel shader [0x80070057] D3D shader create error for vertex shader [0x80070057] ShaderProgram is unsupported, but because jobified rendering is enabled the ShaderProgram can not be removed. ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default There's also a line near the top of the log that says: "it looks like wine32 is missing, you should install it."

I had this issue back in January: I was gone for two weeks on vacation. When I came back home, I found that the parity on my unraid server was no longer valid and it was showing over one-hundred-trillion (?!) reads to the drive, along with over a thousand errors. Ive had this drive in my array since September of last year, so not very long at all. I was unable to get the drive to spin up for a S.M.A.R.T. test, but the server wasn't recognizing it as connected. I replaced the SATA cable and was able to run an extended test; it returned with no errors. Is it safe to assume the issues were due to the SATA cable? Is there something else I should do to test the drive before I start using it again? ST8000VN0022-2EL112_ZA1CJNWE-20190317-1337.txt

Can you update the version of mktorrent to 1.1? https://github.com/Rudde/mktorrent/releases/tag/v1.1

Anyone else think it would be useful to be able to define the order in which docker containers are autostarted in unRAID? Personally, I'm trying to set up an nginx proxy to a few services I'm running on Docker. Initially, I was using jwilder's nginx-proxy. That works really well, but I want to move away from it since most of what it does (sans templating) can be done using links. The only issue I see is though, is that the nginx container would have to be ran last. I suppose I could get around this by not autostarting it and initiating it myself in the case of a reboot. Also, has anyone talked about support for compose in unRAID? That might be a solution to this kind of issue as well.

Awesome; I appreciate the feedback. In the meantime, I can just set up a docker container with nginx and proxy it. Unless someone knows of a better way to do it?

I want to put a self-signed cert on the web interface. Has anyone experimented with this at all?

That might have been the issue. I just changed it to cache only. Thanks!

I'm also having the same issue. http://lime-technology.com/forum/index.php?topic=35918.0

My server rebooted and the containers didn't start up. When I ssh'd into the server to check them, they weren't there. Looking at the syslog, it looks like the docker.img was overwritten but I can't say for sure. Any one else running into this issue? I'm running 6beta10a http://pastebin.com/iCyBqbP4

Oh, I didn't know there was one. Thanks for pointing that out; I found it.

Is anyone still working on the quick-start guide for Btrfs in unRAID?