https://lakefs.io/ logo
#help
Title
# help
g

Giuseppe Barbieri

12/20/2023, 12:12 PM
can you run LakeFS with Podman?
e

Elad Lachmi

12/20/2023, 12:29 PM
lakeFS is available as a docker image and a helm chart I don’t see any reason it wouldn’t run
g

Giuseppe Barbieri

12/20/2023, 12:29 PM
I got this: > Error: short-name "treeverse/lakefs:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"
e

Elad Lachmi

12/20/2023, 12:31 PM
I don’t have experience directly with Podman Just to make sure - you’re able to pull other images from dockerhub?
g

Giuseppe Barbieri

12/20/2023, 12:31 PM
I installed minio with Podman in another VM on the same network
e

Elad Lachmi

12/20/2023, 12:32 PM
Did you pull the minio image from dockerhub?
g

Giuseppe Barbieri

12/20/2023, 12:33 PM
I used quay, but there is also the dockerhub equivalent
e

Elad Lachmi

12/20/2023, 12:33 PM
Can you try
<http://docker.io/treeverse/lakefs:latest|docker.io/treeverse/lakefs:latest>
?
You’re using the CLI or UI?
g

Giuseppe Barbieri

12/20/2023, 12:33 PM
cli
Can you try
<http://docker.io/treeverse/lakefs:latest|docker.io/treeverse/lakefs:latest>
?
sorry for the nub question, but how shall I do that?
e

Elad Lachmi

12/20/2023, 12:34 PM
so try this:
Copy code
podman pull <http://docker.io/treeverse/lakefs:latest|docker.io/treeverse/lakefs:latest>
g

Giuseppe Barbieri

12/20/2023, 12:35 PM
it works, it's pulling
done
e

Elad Lachmi

12/20/2023, 12:38 PM
great!
so for future reference, anything you’re trying to pull from dockerhub needs a
<http://docker.io/|docker.io/>
added to the start of the image name ✌🏻
👍 2
g

Giuseppe Barbieri

12/20/2023, 12:49 PM
I saved the setting up command in a script, by using
podman
instead of
docker
and adding the
<http://docker.io/|docker.io/>
prefix to
treeverse/lakefs:latest
but when I run I get this
e

Elad Lachmi

12/20/2023, 1:02 PM
Yeah, looks like the lakeFS container can’t reach the postgres container over the bridged network
Copy code
connect failed: failed to connect to `host=localhost user=lakefs database=postgres`: dial error (dial tcp [::1]:5432: connect: connection refused)
g

Giuseppe Barbieri

12/20/2023, 1:03 PM
yep, there is no way to get more info about it?
e

Elad Lachmi

12/20/2023, 1:03 PM
More info from lakeFS or from me? 😉
g

Giuseppe Barbieri

12/20/2023, 1:04 PM
😄, more info about the refused connection
lakefs 1
😅 1
I mean, wrong endpoint (wrong port), wrong access key id, wrong secret access key, etc etc
for the endpoint I used http://192.168.11.107:9000
which is the VM local ip, with the port on which I can also connect to manager the UI
actually if I type 9000 I'm being directed at 9090, but I saw other examples using the 9000, so I used that as well
e

Elad Lachmi

12/20/2023, 1:09 PM
I mean, wrong endpoint (wrong port), wrong access key id, wrong secret access key, etc etc
From lakeFS’s perspective, it’s given a host and port, it tries to connect to it, and the connection is refused So first of all, it’s a networking issue - so it’s before any credentials are involved
g

Giuseppe Barbieri

12/20/2023, 1:10 PM
if I can ping that, does this help/mean anything?
e

Elad Lachmi

12/20/2023, 1:10 PM
I’d say that either the postgres container isn’t listening to that port or it is listening to that port, but the port isn’t forwarded to the host
👍 1
if I can ping that, does this help/mean anything?
Not really
👍 1
g

Giuseppe Barbieri

12/20/2023, 1:12 PM
ah wait, postgres is local, only minio lies on the other VM
e

Elad Lachmi

12/20/2023, 1:12 PM
As an example: If a container you’re running listens on port 8080, that doesn’t automatically mean you can put
<http://localhost:8080>
in a Chrome tab and get to the web server hosted in that container and listening to port 8080
g

Giuseppe Barbieri

12/20/2023, 1:13 PM
do you mean that an ip:port combination can either listening or offering a web server?
e

Elad Lachmi

12/20/2023, 1:14 PM
No, there’s a second half to that sentence 😏
👍 1
The container runtime needs to map the port exposed by the container (in this example 8080) to port 8080 (or any other available port) of your local host Only then can you ping
<http://localhost:8080>
and get a response from whatever process is running inside the container
👍 1
So there are several options why you can’t connect to the postgres container: 1. Either the container isn’t running 2. Or the container is running, but fails to fully start up for some reason 3. Or is running and started up, but you have the wrong port 4. Or is running and started up and you’ve got the correct port, but the docker runtime isn’t configured correctly to map the container port to localhost (which is possible, but isn’t a must)
👍 1
g

Giuseppe Barbieri

12/20/2023, 1:20 PM
I didn't use a container for postgres, shall I had?
e

Elad Lachmi

12/20/2023, 1:26 PM
You don’t have to, but I believe that allowing a container to talk to a service (e.g., postgres) running on the localhost also requires some configuration
Initially, it might be easier if both lakeFS and postgres run as containers
Although, it’s do-able, if you want to invest the time to make it happen
g

Giuseppe Barbieri

12/20/2023, 1:29 PM
I wish the how-to on-premises would also list how to set up and config the postgres for newbie like me😔
e

Elad Lachmi

12/20/2023, 1:29 PM
I’m sure there are plenty of tutorials out there
Running postgres locally in a container for local development/experimentation is a very common use case
g

Giuseppe Barbieri

12/20/2023, 1:31 PM
I follow initially this, but I didn't have
adduser
later on and had to follow another one
brb
e

Elad Lachmi

12/20/2023, 1:32 PM
Well, that’s part of the journey… That’s the best way to learn
Try stuff Make mistakes
Work through it and figure it out
2 Views