CAN LAKEFS WORK IN AN ISOLATED AIR-GAPPED ENVIRONMENT? I have a LakeFS version 1.14.0 container in an on-prem isolated environment with no internet access. Using postgres for KV store and local block storage for now. After setting the check_audit_url to 127.0.0.1 and log level = none I was able to least get the home page but it is blank. F12 reveals some CSS and body with some cross origin links. I can't find any logs that show an error. docker logs lakefs simply shows instruction slike "If you are running LakeFS locally for the first time, then complete setup process at http://127.0.0.1/setup". But that setup link gives me a blank page. Appreciate any help possible. Thanks!

Hi @Sam - lakeFS can work in an isolated air-gapped environment. No need whatsoever for internet access.

We got a LakeFSversion 1.14.0 container already on an air-gapped network, that I installed on RHEL 8.9 server along with a postgres container. I am able to get LakeFS to talk to Postgres. When I do - docker run .... lakefs:latest run --config /etc/lakefs/config.yaml - the server seems to come up fine. Then from browser http://127.0.0.1:8000 I get blank page. F12 does show some stylesheets got downloaded but no errors. Just blank page.

Hi @Sam Can you please generate a HAR file from browser and share it?

I will. Thanks.

@Sam Can you please revert all configuration changes and simply run

lakefs run --local-settings

, for testing purposes? Please send me the lakeFS logs when done

ok.. Same issue runnig with local settings but I will.. I have the output from "docker logs lakefs". Anything else?

Can you attach the lakeFS logs here?

@Sam Any update on this thread?

It works locally now... I just reinstalled lakefs on a different ec2.. with docker-ce instead of podman. No clue why that would make a difference. But don't have the luxury to continue troubleshooting with podman. Consider this issue closed. Thanks.

Thanks for the update