-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use github service containers instead of docker compose #82
Conversation
nopcoder
commented
Oct 15, 2023
•
edited
Loading
edited
- replace lakectl setup with lakefs installation env vars
- remove unused repo creation with s3 storage namespace
- removed docker-compose to spin lakefs service. using container service.
- use curl user/password instead of format basic auth
- setup lakefs using env - no need to maintain another docker-compose for lakefs - use curl basic auth (consider replace with lakectl)
7ffd6fa
to
b8fd258
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat, thanks!
Just please make sure there is some way to access lakeFS server logs.
- name: lakeFS logs | ||
if: ${{ always() }} | ||
run: docker-compose -f ops/docker-compose.yaml logs --tail=1000 lakefs | ||
command: docker exec lakefs ls lakefs/data/block/data/symlinks/example-repo/example-branch/path/to/symlink.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this loses the logs? Or does GitHub keep them for the service container?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub dump the services logs at the end as part of the post processing, ex: https://github.com/treeverse/airflow-provider-lakeFS/actions/runs/6533424810/job/17738585733?pr=82