theiam79
-
Posts
41 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by theiam79
-
-
Thanks. I ended up getting it working, but was mostly curious how you persisted across reboots.
-
On 5/7/2020 at 1:49 AM, Thx And Bye said:
I have add a alias that launches docker-compose in a container. It has the benefit of being up-to-date without any modifications:
alias docker-compose='docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ -v "$PWD:$PWD" \ -w="$PWD" \ docker/compose:latest'It has worked great so far for me.
Interested in doing this, as it seems like its a relatively easy to maintain solution. Would you mind sharing your steps? I'm fairly new to some of the advanced features of Docker.
-
Keep up the good work, been rock solid for the last 4 years.
-
Just thought I'd report back, upgrading to 6.4.1, removing the IP from eth1 and configuring the docker network the container picks up the correct gateway and everything works flawlessly. Thanks for all the help!
-
I'm using pfsense, so adding virtual IPs is easy
-
Can I leave some containers on br0 and then use eth1 for others if I point out to a different gateway on the same subnet?
-
Alright, I'll try and give that a look tonight
-
@bonienl
Tried messing with it some tonight, wanted to see if using a bridge instead of directly connecting to eth1 made a difference. Unfortunately it did not. From the link you provided it looks like I should be able to use both NICS on the same subnet as long as they point to different gateways, but my container is still taking 192.168.1.2 as the gateway with eth1 set to use 192.168.1.11. Any other thoughts as to what could be the cause? I'd really prefer not to have to go to a different subnet as I currently have this reverse proxied and don't want to break that. -
21 hours ago, theiam79 said:
Alright, so I set up an IP alias for my lan in pfsense, and set eth1 to use that. After deleting and restarting docker the container still used 192.168.1.2 as the gateway. I tried manually deleting and creating the network with the new gateway, and got an error about it already being in use. I then created a second alias on pfsense and made a custom network specifying that as the gateway, and then choosing that and manually passing an ip param in the advanced options.
-
Alright, so I set up an IP alias for my lan in pfsense, and set eth1 to use that. After deleting and restarting docker the container still used 192.168.1.2 as the gateway. I tried manually deleting and creating the network with the new gateway, and got an error about it already being in use. I then created a second alias on pfsense and made a custom network specifying that as the gateway, and then choosing that and manually passing an ip param in the advanced options.
-
Ah, that makes sense, I'll take a look tonight or tomorrow and report back, thanks for the help!
-
-
After it clears it comes back the same way
-
"NetworkSettings": { "Bridge": "", "SandboxID": "94842cd874bb3ddb54dcd527436d33f716628af320e08ef8b194dd35f752f829", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": {}, "SandboxKey": "/var/run/docker/netns/94842cd874bb", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null, "EndpointID": "", "Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "IPAddress": "", "IPPrefixLen": 0, "IPv6Gateway": "", "MacAddress": "", "Networks": { "eth1": { "IPAMConfig": { "IPv4Address": "192.168.1.122" }, "Links": null, "Aliases": [ "189987dcde57" ], "NetworkID": "30e822af550842c5c44ee66f4ff5189256a0adfc65f3cde8234539319bbfd4f0", "EndpointID": "888872d1dfb62147f519d9efc882802792ac86c7182a7126a9ef982f9886b3fe", "Gateway": "192.168.1.2", "IPAddress": "192.168.1.122", "IPPrefixLen": 24, "IPv6Gateway": "", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "MacAddress": "02:42:c0:a8:01:7a", "DriverOpts": null } } } } ] -
On mobile ATM so I can try to get you the inspect output if you need. I am unable to ping out from the container, even local addresses appear to do nothing.
-
20 minutes ago, bonienl said:
Make sure you have included a gateway address in the static assignment of eth1.
Yeah I've got that in there. I've attached an image of my eth1 config as well as the container network settings
A sidenote, not sure if this is expected but if you change or remove a network config that a container uses (such as changing eth1 to be a bridge), even if it does not auto start, you can no longer make changes to it or use that template due to a missing csrf token error and have to manually recreate it
-
@bonienl Was wondering if I could get some help with this. Server has a quad NIC, and I'd like to take one of those and use it for one specific container, leaving the rest as they are (at least for now). I set the eth1 interface up with a static IP, and I'm able to choose that interface in the container template. When I start the container I am able to ping it locally just fine, but it cannot reach the internet. I've been all over the forums looking for an answer, and I'm sure its just me missing something, but any help would be appreciated.
-
Did you ever get anywhere with this? I've been playing with it some but haven't been able to get it working
-
Don't really know how to tell since I lost the option to VNC into it.
-
Well, I'm back. I can assign the IGD and save those settings, but when I try to boot up my VM I can't RDP into it, or even ping it for that matter. Both of these work fine when I have it set to VNC. VM is running Windows Server 2012 fwiw.
-
13 hours ago, Kireo said:
Some motherboards have vt-d setting you have to turn on, not only vt-x. Manufacturer call it different things and can place it in another menu in BIOS.
Thanks for the help, that did the trick. Knew I was missing something easy lol.
-
I've been trying to set this up with no luck. I have a VM, using SeaBIOS and i440FX-2.7, but in the VM settings for GPU my only option is VNC still. I'm sure there is something simple I'm missing, but I'm not knowledgeable enough to find it. I'm currently running 6.3.5, and my CPU is a 4690K.
-
I had DDNS handled through my router configured with Google Domains so I'm not sure what the deal is, but I'll get back to it tomorrow.
-
Yep, switched to that one haha. Probably wont be able to work on it til later, probably need to switch to ddclient too since I'm still seeing that error
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted
Running in to an issue with valheim - when I stop/restart the container, it renames the current {world}.db file to {world}.db.backup and then generates a new db file that is significantly smaller than the existing one. When the server does load with that db, the world is reset back to normal. Any idea what's causing this?