CaptainMagnus Posted March 9, 2021 Share Posted March 9, 2021 (edited) Problem: When I restart my unraid server, wireguard can't reach my docker containers. In order to get that working, I have to stop docker and then start it again. When I do that, something strange happens with my NIC, so I now have to disconnect and reconnect the network cable in order for network connectivity to be restored. After I've done the above, wireguard can now connect to docker containers. Question: Is there a way to make sure wireguard starts before docker or otherwise have this functionality work after a reboot? Cheers, Magnus Edited March 10, 2021 by ChatNoir -wireshark +wireguard Quote Link to comment
trurl Posted March 9, 2021 Share Posted March 9, 2021 On the Docker page, you can change the order of startup of your containers by dragging. Move the slider from Basic to Advanced and you can specify a delay after each. Quote Link to comment
CaptainMagnus Posted March 10, 2021 Author Share Posted March 10, 2021 8 hours ago, trurl said: On the Docker page, you can change the order of startup of your containers by dragging. Move the slider from Basic to Advanced and you can specify a delay after each. I don't need to start docker containers in a different order, I need wireshark to start before docker when unraid boots up Quote Link to comment
ChatNoir Posted March 10, 2021 Share Posted March 10, 2021 1 hour ago, CaptainMagnus said: I don't need to start docker containers in a different order, I need wireshark to start before docker when unraid boots up Well, since Wireshark is a Docker container, I am not sure how it would be up and running before the Docker service is active. Quote Link to comment
CaptainMagnus Posted March 10, 2021 Author Share Posted March 10, 2021 11 hours ago, ChatNoir said: Well, since Wireshark is a Docker container, I am not sure how it would be up and running before the Docker service is active. That's because I'm an idiot. I don't mean wireshark, I mean wireguard 🤯 1 Quote Link to comment
ChatNoir Posted March 10, 2021 Share Posted March 10, 2021 I edited your first post and title to reflect that, it will be better for clarity in the future. 1 Quote Link to comment
ljm42 Posted March 11, 2021 Share Posted March 11, 2021 WireGuard starts early in the boot process, after networking but before the array starts. Docker doesn't start until after the array starts. So the boot order is already correct. I'd suggest uploading diagnostics after you've restored networking connectivity, maybe someone will see a clue. Quote Link to comment
automationgeek Posted July 26, 2022 Share Posted July 26, 2022 I have the same issue, wondering if you found a solution ? Quote Link to comment
Recommended Posts
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.