7
Haxk20
217d

Fucking docker on arch linux. Jeeez fucking hell.
Use docker to run the wallet they said. It works just fine they said. Fuck that.
Internet is not working in docker and i have no clue why. Hours into debugging it and still nope.
If anybody has more experience with docker on arch then please tell me how to fix this shit. Yes i have tried sudo sysctl net.ipv4.conf.all.forwarding=1 and sudo sysctl net.ipv4.ip_forward=1
Both of which did bullshit. Still no internet. Fuck this shit.

Comments
  • 0
    Have you enabled the docker network service?

    Docker is working just fine for me.
  • 0
    @olback What now ? There is nothing like that in documentation. I have done systemctl enable and start docker but idk if thats network service
  • 1
    @Haxk20 might have gotten VMware an docker mixed up in my mind..
  • 0
  • 0
    @olback Yeah vmware has network service. Docker as far as i know doesnt. For me it just refuses to work properly. Weird.
  • 0
    Ohhhhh socket. Will try that
  • 0
    Nope still very much broken
  • 0
    You probably know more than me but what network stack are you using? systemd/NetworkManager/...?
  • 0
    @olback network manager. Jeeez systemd managing network ? Oh god no thank you.
  • 1
    @Haxk20 Ok, is it just DNS or does nothing work?
  • 0
    @olback not even ping.
  • 1
    @Haxk20 Have you considerd that something in linux-next might be broken? Have you tried yesterdays kernel? :p
  • 0
    @olback im ashamed to say this but i have tried 5.4.3 and broken there too.
  • 1
    @Haxk20 Is the image broken? Does the image have network at all? Can you ping the image?
  • 0
    @olback its official debian image. Im pretty sure network is part of it.
  • 0
    I spun up a debian:latest image and got two new network interfaces:
  • 0
    But k will figure it out tomorrow. Now sleep is the only thing i want.
  • 0
    Yup j have two too.
  • 1
    Well, I don't know whats up :shrug:

    Good luck!
  • 1
    Step 1: disable docker's stupid iptables autoconfiguration (because it automatically adds rules to let your containers be directly exposed to the internet - wtf)

    Step 2: manually configure the subnets you want docker to use

    Step 3: create forwarding rules in your iptables *filter table, and postforwarding rules in the *nat table

    Step 4: spend days combing through every little configuration mistake

    Step 5: kill yourself a few hundered times

    Step 6: ???

    Step 7: Profit!

    (Can you tell that I've been through this as well? I'd be sharing sample config files with you, but it's really late, and just the idea of touching that stuff again fills me with dread and despair - not how I wanna go to sleep tonight. But if you're really desperate ping me, and I'll try to help)
  • 0
    @endor config files would be really really nice. Thanks man
  • 1
    @Haxk20 Here you go: https://pastebin.com/dKBV5Wuw

    Sorry for taking so long, yesterday I tried to update ubuntu 16 to 18 on my laptop (why did I even do that?) and it borked everything and I had to spend all day to fix that shit.

    Paste expires in a week, you should save it if you want it for future reference.

    Btw: if anyone finds any mistake or has any suggestions to improve the setup, please let me know. I *think* I understand how almost everything works in there, but sometimes things behave in unexpected ways, because fuck consistency.
  • 1
    @Haxk20 Oh shit I forgot: if you want your docker-compose to use the network you created, you have to replace the 'networks' tag in the container definition with:

    network_mode: bridge

    So it's like

    container:

    image: bla

    ports: bla

    network_mode: bridge

    (Edit: oh right, devrant removes leading whitespace. Fuck it, I tried - let me know if you don't understand)
  • 0
    @endor thanks. Will try to fix it.
Add Comment