mengw15 opened a new issue, #6032: URL: https://github.com/apache/texera/issues/6032
`bin/bootstrap-lakekeeper.sh` runs Lakekeeper natively on the host. It was added because, at the time, running Lakekeeper in Docker did not work for local development: the warehouse's S3 endpoint was registered as a Docker-internal hostname (`texera-minio:9000`) that the host-native Texera could not resolve, while switching it to `localhost` broke the Lakekeeper-container → MinIO connection. So the REST catalog required Lakekeeper to run on the host. `bin/local-dev.sh` (#5961) now starts Lakekeeper in Docker and sets the S3 endpoint to the host's LAN IP, which is reachable from both the host-native Texera and the Lakekeeper container. I verified the REST-catalog path end-to-end with `local-dev.sh`: workflow results are written to the `texera-iceberg` MinIO bucket through Lakekeeper. Since Docker Lakekeeper now works, `bin/bootstrap-lakekeeper.sh` is redundant and can be removed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
