Skip to content
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

Starting stack with docker compose produces a "curl not found" error #232

Open
gschmutz opened this issue Nov 14, 2024 · 0 comments
Open

Comments

@gschmutz
Copy link

Hi

I'm just checking out LakeFS, meaning I'm pretty new to the project. Yesterday I have tried to use the docker compose stacks provided here and I got into the following error when starting it using the local-lakefs profile:

lakefs-1            | /app/wait-for: exec: line 29: curl: not found
lakefs-1            |
lakefs-1            | ------------------------------------------------
lakefs-1            |
lakefs-1            |       MinIO admin:   http://127.0.0.1:9001/
lakefs-1            |
lakefs-1            |                      Username : minioadmin
lakefs-1            |                      Password : minioadmin
lakefs-1            |
lakefs-1            | ------------------------------------------------
lakefs-1            |
lakefs-1            |
lakefs-1            |       Jupyter:       http://127.0.0.1:8888/
lakefs-1            |
lakefs-1            | ------------------------------------------------
lakefs-1            |
lakefs-1            | lakeFS Web UI: http://127.0.0.1:8000/      >(._.)<
lakefs-1            |                                              (  )_
lakefs-1            |
lakefs-1            |                 Access Key ID    : AKIAIOSFOLKFSSAMPLES
lakefs-1            |                 Secret Access Key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
lakefs-1            |
lakefs-1            | -------- Let's go and have axolotl fun! --------
lakefs-1            |

with the effect that the quickstart repository is not created.

The problem of course is obvious. The lakefs docker image is not/no longer? including the curl command.

Yesterday I was thinking about an alternative using wget and I have a working solution in local environment. I can provide a pull request, if this is a solution you would support. I'm asking before doing the PR, as there are quite a few places where it needs to be changed.

An alternative would be of course to install curl in the docker image, but that would have to be done at image build time.

Thanks
Guido

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant