I ran into a problem using the aws cli v2 with step 3 in the example: https://docs.lakefs.io/quickstart/aws_cli.html

aws --endpoint-url=<http://s3.local.lakefs.io:8000> --profile local s3 ls

I use the docker variant for the cli using the bash alias:

alias aws='docker run --rm -it -v ~/.aws:/root/.aws amazon/aws-cli:latest'

receiving a timeout message I fixed this by reverting to the awscli v1 and disabling the v2 docker awscli alias

Hey George, thanks for reporting this. I’m unable to reproduce this on my machine. Could you run the

aws

command with the

--debug

option and copy the logs here (or even better, open a github issue)?

one sec

<http://s3.local.lakefs.io|s3.local.lakefs.io>

resolves to 127.0.0.1. Assuming you are running lakeFS locally, using the aws cli from a different container in a different network won't be able to reach it.

I am just stepping through the quickstart example and finding a disconnect between the object names between the various pages: eg https://docs.lakefs.io/quickstart/repository.html: create repository

my-repo

with branch master then in the next page when drilling through the copy file link to https://docs.lakefs.io/quickstart/aws_cli.html: then the repo has changed to

example

Sorry for the inconvenience with the naming, we're actively working on making it more consistent. https://github.com/treeverse/lakeFS/issues/2043

all good just stepping through and sharing the experience