[Support] Clowrym's Docker Repository


clowrym

Recommended Posts

On 2/21/2019 at 8:19 PM, mgranger said:

yes i am trying to get the webui from a computer that is on 192.168.1.x

Did you ever find a solution? I'm having a similar problem. My log doesn't seem to have a specific error so I'm a little lost.

 

Using OpenVPN provider: PROXPN
Supplied config US Seattle.ovpn could not be found.
Using default OpenVPN gateway for provider proxpn
Setting OPENVPN credentials...
adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0
Thu Mar 14 04:35:51 2019 us=492872 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=492939 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=492948 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=493143 Current Parameter Settings:
Thu Mar 14 04:35:51 2019 us=493159   config = '/etc/openvpn/proxpn/default.ovpn'
Thu Mar 14 04:35:51 2019 us=493169   mode = 0
Thu Mar 14 04:35:51 2019 us=493177   persist_config = DISABLED
Thu Mar 14 04:35:51 2019 us=493184   persist_mode = 1
Thu Mar 14 04:35:51 2019 us=493190 NOTE: --mute triggered...
Thu Mar 14 04:35:51 2019 us=493213 326 variation(s) on previous 5 message(s) suppressed by --mute
Thu Mar 14 04:35:51 2019 us=493221 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Thu Mar 14 04:35:51 2019 us=493235 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 2.08
Thu Mar 14 04:35:51 2019 us=493759 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Thu Mar 14 04:35:51 2019 us=493769 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Mar 14 04:35:51 2019 us=494322 LZO compression initializing
Thu Mar 14 04:35:51 2019 us=494393 Control Channel MTU parms [ L:1622 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Thu Mar 14 04:35:51 2019 us=494436 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ]
Thu Mar 14 04:35:51 2019 us=494464 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 512,key-method 2,tls-client'
Thu Mar 14 04:35:51 2019 us=494471 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize512,key-method 2,tls-server'
Thu Mar 14 04:35:51 2019 us=494481 TCP/UDP: Preserving recently used remote address: [AF_INET]50.7.88.172:443
Thu Mar 14 04:35:51 2019 us=494509 Socket Buffers: R=[212992->212992] S=[212992->212992]
Thu Mar 14 04:35:51 2019 us=494518 UDP link local: (not bound)
Thu Mar 14 04:35:51 2019 us=494525 UDP link remote: [AF_INET]50.7.88.172:443

 

Link to comment
1 hour ago, clowrym said:

Is your PUID & PGID set to 0 for a reason? I dont know if it will make a difference, but usually I keep my dockers at PUID=99 AND PGID=100.... thats the only thing that looks a little off to me

That's discouraging, I was hoping I was missing something obvious. I set them to that because I was logged in as root and I checked the ID and it was 0 for both. It was a desperate attempt to get it working.

Link to comment
  • 3 weeks later...

This docker is no longer working for me. Unable to debug it too. It keeps going through the process of grabbing all of the OPVN files from NordVPN and running that through sed to format all of them. It dies after a few minutes and restart all over again.

 

Any suggestions to figure out what is happening here, or has this been abandoned?

 

Link to comment
23 hours ago, snowboardjoe said:

This docker is no longer working for me. Unable to debug it too. It keeps going through the process of grabbing all of the OPVN files from NordVPN and running that through sed to format all of them. It dies after a few minutes and restart all over again.

 

Any suggestions to figure out what is happening here, or has this been abandoned?

 

I can Help you with setting up the Docker etc, but I've only created the templates, if your having issues that dont relate to docker template settings, you can post HERE.

 

One thing to note, if you arent Using PIA for your provider, you need to change the entries in the "OPENVPN_CONFIG:" variable to suit your providers config file names, they can be found HERE in your providers folder.

Edited by clowrym
Link to comment
On 4/8/2019 at 2:44 PM, snowboardjoe said:

This docker is no longer working for me. Unable to debug it too. It keeps going through the process of grabbing all of the OPVN files from NordVPN and running that through sed to format all of them. It dies after a few minutes and restart all over again.

 

Any suggestions to figure out what is happening here, or has this been abandoned?

 

I wonder if your issue is related to this?

 

https://github.com/haugene/docker-transmission-openvpn/issues/764

 

Link to comment
On 4/10/2019 at 11:49 AM, clowrym said:

I wonder if your issue is related to this?

 

https://github.com/haugene/docker-transmission-openvpn/issues/764

 

 I looked more into this today, but still unable to get it running again. The docker.log reports:

time="2019-04-15T13:58:23-05:00" level=info msg="shim reaped" id=79a57e2ec068e23e5876a15802ec53bca5e21b02ecb518862be57b1d734a32aa 

time="2019-04-15T13:58:23.298963594-05:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

time="2019-04-15T13:58:23.316022846-05:00" level=warning msg="Failed to delete conntrack state for 172.17.0.13: invalid argument"

time="2019-04-15T13:58:24-05:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/79a57e2ec068e23e5876a15802ec53bca5e21b02ecb518862be57b1d734a32aa/shim.sock" debug=false pid=27205 

 

The log for the container itself is empty. Not sure what else to look at. Installed deludge and that's running, but would like to go back to Transmission if possible.

Link to comment
  • 2 weeks later...

But now I cannot get a server to run and this log entry from /var/log/mineos.log is kind of vague.  Any thoughts on fixing this?

 

{"level":"info","message":"[testing] received request \"start\"","timestamp":"2019-04-30T02:46:35.985Z"}
{"command":"start","uuid":"2bbb5d00-6af2-11e9-b791-ab42d78053ab","time_initiated":1556592395984,"success":false,"err":"!up","time_resolved":1556592396086,"level":"error","message":"[testing] command \"start\" errored out:","timestamp":"2019-04-30T02:46:36.087Z"}

 

Link to comment

While I do run a couple server's, ive never run into any of these issues, Typically when I have had issue with starting servers, it was either user:group issues of the files within the mount points, or share mapping. Can you post your docker run command? Beyond any glaring issues there, you could also post an issue HERE

Link to comment

Not sure where to get that.  I am using this all from UnRaid.  So it is just choose it from the list, download it, and then select start.  /var/log/docker.log doesn't show anything in there for the command run.  This is the command PS info for the correlating process that started when the mineos container restarted. 

docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/82a7ab3eb8643a40f8f2933559da556ed50bdfd8a2f021b4dbf5f9979d05fade -address /var/run/docker/containerd/docker-containerd.sock -containerd-binary /usr/bin/docker-containerd -runtime-root /var/run/docker/runtime-runc

 

Link to comment
15 hours ago, bobbo489 said:

Not sure where to get that.  I am using this all from UnRaid.  So it is just choose it from the list, download it, and then select start.  /var/log/docker.log doesn't show anything in there for the command run.  This is the command PS info for the correlating process that started when the mineos container restarted. 


docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/82a7ab3eb8643a40f8f2933559da556ed50bdfd8a2f021b4dbf5f9979d05fade -address /var/run/docker/containerd/docker-containerd.sock -containerd-binary /usr/bin/docker-containerd -runtime-root /var/run/docker/runtime-runc

 

CLick force resart and a window should pope up, your looking for this:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='MineOS-node' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'USER_PASSWORD'='password' -p '25565-25575:25565-25575/tcp' -p '8443:8443/tcp' -p '8120-8126:8120-8126/tcp' -p '25565:25565/udp' -v '/mnt/cache/appdata/minecraft/':'/var/games/minecraft':'rw' -v '/mnt/cache/minecraft':'/mnt/data':'rw' 'hexparrot/mineos' 
479fd653a593c9ed8f3c2b7e150b6c26e540c50b6cb593d4964337fad4dace05

Also, 

 

can you check the user:group on the folders / subfolders, they all should be 1000:1000 per below

 

 

 

 

 

image.png

Edited by clowrym
Link to comment

I'm having this problem with the transmission docker container. 

 

Is this a problem? because I want to get rid of this annoying message. I'm using PIA 

 

ErrorWarningSystemArrayLogin


Sun May 5 05:13:18 2019 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2687837 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Sun May 5 05:13:18 2019 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2687838 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
 

Link to comment
8 hours ago, gacpac said:

I'm having this problem with the transmission docker container. 

 

Is this a problem? because I want to get rid of this annoying message. I'm using PIA 

 

ErrorWarningSystemArrayLogin


Sun May 5 05:13:18 2019 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2687837 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Sun May 5 05:13:18 2019 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2687838 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
 

Do you have this added :

 

image.thumb.png.08b0f70cfe54fd9bf1990eb403268869.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.