https://lakefs.io/ logo
Join Slack
Powered by
has anyone encountered this issue? and how did you...
# help
j
has anyone encountered this issue? and how did you resolve it?
y
Hey @jurgen, welcome! In order for this to work, you need to let lakeview know which region your bucket is in. To do so, you can use an environment variable, so your command becomes (for example):
Copy code
docker run -e AWS_DEFAULT_REGION=us-east-1 -it -p 5000:5000 -v $HOME/.aws:/home/lakeview/.aws treeverse/lakeview:0.1.0 --table tbl_s3inventory --output-location <s3://xxx-test-bucket-01-athena/>
It seems like this blog post has gotten a bit out of date, I'm sorry about that. I've opened an issue so that the team goes over it.
j
Thank you very much @Yoni Augarten I thought it must be something like this but I had no way of telling what the command line options are. I did look through all the code, but quite quickly
👍 1
I'm sorry to bother you once more @Yoni Augarten I've made progress and am now greeted with the lakeview banner and 'unable to locate credentials' when I access the webpage. Am I missing some documentation, or do you know if I need to supply these credentials via command line switches? Many thanks.
i
Hey @jurgen, does your 
$HOME/.aws/credentials
file contains valid AWS credentials? You can also pass AWS credentials to the docker in a similar way to the region: 
…. -e AWS_ACCESS_KEY_ID=<your_access_key> -e AWS_SECRET_ACCESS_KEY=<your_secret_access_key> .....
j
thanks you @Itai Admi I actually tried that, however I didnt place a '-e' infront of each. I also tried to edit the Dockerfile and add the env's to that.
It looks like its working now... although it the page is stuck with the spinning loading wheel. I need to figure out whats wrong now. Appreciate your help.
Perhaps its some kind of permission issue on the bucket - no output on the lakeview console
i
That’s interesting, do you have athena access with these credentials? I wonder if lakeview was able to run the queries
j
I should point out I am running this on an EC2 instance. I'm not sure if that is the intended location, but worth pointing out
I've had a look at athena 'recent queries' nothing there.
i
Do you see any logs from 
lakeview
? Requests & responses made from the browser to the app could also help debugging it
j
@Itai Admi where would be the best place to look for logs?
i
If your running it using docker on EC2, then 
docker logs <Container_ID>
From that EC2 instance
j
thanks. it shows nothing outside of the lakeview banner. I've also had a look through the cloudwatch logs and cant see anything of interest
i
Do you see anything from the browser’s requests & responses?
j
no nothing either.
I am trying to ask my security team if perhaps requests for querying athena are hitting the firewall. I'm not sure exactly how lakeview calls this, but I assume its using boto
if its using urllib3, depending on the version it doesnt handle proxies well
i
Look at the browser's devtools, under the network tab, before and during the loading spinning wheel. It should be visible which request to lakeview isn't working.
j
thanks, I'm pretty sure its trying to hit the proxy
I've done a test albeit outside of docker, but on the same ec2 instance with 'aws s3 ls s3://xxx" and it fails trying to go via the proxy
👍 1
8 Views
Open in Slack
PreviousNext
Powered by