Dolt seems ignoring proxy setting in container, stops by proceeding jobs

[kbmuellerdo]

We're proceeding an POC of Dolt concidering commerical usage of the tool for our data team. But after setup of Dolt we're facing issues using jobs in dolt. We are able to create tables and commit content via gui on doltserver via spreadsheet and query. But working with jobs ends in stucking processing on UI. You'll only see a circling "processing".

Job status delivers following errormessage:

The system is running behind a ZScaler proxy and a firewall. We see some traffic on the proxy from dolt but due the time of processing no traffic at the proxy log which indicates that the job is trying to connect directly to github and not over the proxy.

We send our proxyconfig and certifcate to all dolt containers but it seems that some services didn't take the proxyconfig correctly. We have no clue which service on which container behaves wrong.

Any ideas?

[timsehn]

I'm going to move this to the DoltLab queue.

@coffeegoddd will respond this morning.

That said, this seems like a problem that may be able to be fixed by: https://www.dolthub.com/blog/2024-10-03-how-to-run-doltlab-without-egress/

[coffeegoddd]

@kbmuellerdo Thanks for the issue. At a glance, this does appear to be an issue caused by your firewall which is preventing the Dolt binary in the DoltLab job from calling api.github.com to check for the latest dolt releases when dolt version is run.

This should be fixed in the latest DoltLab version, v2.3.3, so upgrading should fix the error you see above. Additionally, if your firewall is blocking egress calls to public.ecr.aws where DoltLab service images are hosted, you should follow the steps in the blog @timsehn linked in his response, and pre-load the images on the host using docker load.