[SOLVED] Is there someone who succeed to make Dagger working on a GitLab server?

[lilac kayak]

Since days, I'm trying to be able to start Dagger on my self-hosted GitLab server but didn't succeed. I've already tried during hours and I would be so happy if it can works. I'm quite tired of writing unmanagable yaml files. My current issue on Github : https://github.com/dagger/dagger/issues/9074

If someone has an idea... Many thanks in advance !!!

[mental egret]

@lilac kayak what OS is your gitlab server current running in?

[lilac kayak]

Operating System: Red Hat Enterprise Linux 8.10 (Ootpa)
CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
Kernel: Linux 4.18.0-553.30.1.el8_10.x86_64
Architecture: x86-64

[mental egret]

can you try running sudo modprobe iptable_nat in the host to see if that solves the issue? ref: https://docs.dagger.io/troubleshooting/#dagger-restarts-with-a-cni-setup-error

[lilac kayak]

TREMENDOUS!!! This indeed solve the issue. Thanks a lot! I was blocked on this since days.

[SOLVED] Is there someone who succeed to make Dagger working on a GitLab server?

[mental egret]

glad this helped, sorry for not seeing this before. 🙏

@cerulean coral WDYT about adding support in the engine to automatically remediate this type of issues?

TBH I'm not sure if / how docker currently overcomes this

[cerulean coral]

hm, we could definitely have a better error message

not 100% sure about loading modules into the kernel automatically though 🤔 🤔 guess we could try!

[mental egret]

I was trying to see how / if docker handles this

I'd assume docker might fallback to the userland proxy maybe if the nat module is not loaded in the kernel? 🤔

[cerulean coral]

i actually don't know - i guess you could disable the module, and then see how docker does it

[mental egret]

good call 😄

[mental egret]

ok.. interesting.. in my case, if I remove the kernel module and I restart the engine it get re-added automatically 😬