Does anybody know how to skip or mimic the /app/wait-for function in the entrypoint of the docker file? I have a situation where the container keeps exiting because it receives an error at this point.

Hi @Walter Johnson, can you please provide more information about your situation. the

wait-for

function waits until

postgres

is up. it runs this script. you could skip it by editing the docker-compose file and removing

"/app/wait-for", "postgres:5432", "--",

But you will probably experience some other error.

I am using Terraform and my postgres instance is setup before and I am certain it is there before I need lakeFS.

How did you confirm that?

I have another container running that I am able to connect to my pg instance with.

can you please send here the connection string you are using to connect?

what is Opostgres ?

Please dont let that be it....😄

😅

My container still shut down.

If you’d like to use 0postgres, you should edit the run command and the properies as well

entrypoint: ["/app/wait-for", "postgres:5432", "--", "/app/lakefs", "run"] -> entrypoint: ["/app/wait-for", "0postgres:5432", "--", "/app/lakefs", "run"]

- LAKEFS_DATABASE_CONNECTION_STRING=<postgres://lakefs:lakefs@postgres/postgres?sslmode=disable> -> - LAKEFS_DATABASE_CONNECTION_STRING=<postgres://lakefs:lakefs@0postgres/call-center?sslmode=disable>

nc -z postgres 5432 returns nc: getaddrinfo: Try again

Sorry but I am not following, which container ?

The lakeFS container.

Can you please share your docker-compose file ?

I am using Terraform not docker compose, it is very similar though.. It just pulls the latest image from treeverse/lakefs and run docker run on that. Here is the relevant code.

resource "docker_container" "lakeFS" {
  image = docker_image.lakeFS.name
  name  = "LakeFS"
  env = [
    "LAKEFS_AUTH_ENCRYPT_SECRET_KEY=secret",
    "LAKEFS_DATABASE_TYPE:postgres",
    "LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING=<postgres://lakefs:lakefs@postgres:5432/call-center?sslmode=disable>",
    "LAKEFS_BLOCKSTORE_TYPE=local",
    "LAKEFS_BLOCKSTORE_LOCAL_PATH=/home/lakefs",
    "LAKEFS_GATEWAYS_S3_DOMAIN_NAME=<http://s3.local.lakefs.io:8000|s3.local.lakefs.io:8000>",
    "LAKEFS_LOGGING_LEVEL=INFO",
  "LAKEFS_COMMITTED_LOCAL_CACHE_DIR=/home/lakefs/.local_tier"]
  ports {
    internal = 8000
    external = 8000
  }
  hostname = "localhost"

  logs     = true
  must_run = true
  attach = false

  entrypoint = ["/app/wait-for", "postgres:5432", "--", "/app/lakefs", "run"]
 

}

try

/app/wait-for 0postgres:5432

I switched that to postgres. It was a type.

Oh ok

I have to assume lakefs cant make any outside connections because I have verified that I can remotely connect to my pg instance.

That’s a good question, lakeFS is quite limited,

That is why I am wondering if there is amy way to mimic a positve response from /app/wait-for in the entrypoint

you could run

nc  postgres 5432

So could I just return a 1 or something at that point, I tried miserably to attempt something like that but I am not the best bash coder.

I would start by running a different image ( instead of lakeFS ) and trying to connect with that image

nc: getaddrinfo: Try again

Seems like its failing to get the address

~ $ nc -zv postgres 5432 nc: getaddrinfo: Try again ~ $ nc -zv localhost 5432 nc: connect to localhost port 5432 (tcp) failed: Connection refused nc: connect to localhost port 5432 (tcp) failed: Connection refused nc: connect to localhost port 5432 (tcp) failed: Address not available ~ $ nc -zv 0.0.0.0 5432 nc: connect to 0.0.0.0 port 5432 (tcp) failed: Connection refused

You could skip it

What if I already have Postgres running and I am certain of it?

I understand, I am also certain of that. But lakeFS doesn’t manage to connect to it for some reason

When the instance starts up is it impossible to skip or mimic the outcome wait-for?

OK, I might of got you wrong at the start, thought you already tried without wait-for and it failed. try changing

entrypoint = ["/app/wait-for", "postgres:5432", "--", "/app/lakefs", "run"]

to

entrypoint = ["/app/lakefs", "run"]

I did but will try it again just for my own sanity.

What happened when you did it?

The container exits immediately and I cant even ssh into for a few seconds.

So lakeFS probably fails when trying to connect to the database ( nothing to do with

wait-for

now )

So this is basically some port issue. I can start lakeFS fine with docker compose.

Port or domain resolving

can app run be more verbose?

Are you seeing any errors?

I am not seeing errors. I start the instance that download and look at the nc function in there and I need to get my hostname to resolve to postgres. That is what will make lakeFS happy and I want to make lakeFS happy. 😁 Time to go further down the rabbit.

If you can provide here the configurations you are using to run both lakeFS and postgres I will try to run it on my end and see if I can reproduce it.

All of your help was super enlightening. I think I will track down the issue shortly.

OK, I am familiar a bit with terraform. Waitingto hear about your progress. Good luck

I am off to bed a sad little man. I did not solve my issue but I did get one more piece of valuable knowledge. I was able to get into the lakeFS server and run nc -zv {IP-OF-MY-PG-INSTANCE} 5432 and it successfully connected. So I put that in the wait-for function and the container exits with errors but that makes me believe there is a problem with the connection string but I can't seem t locate it yet. Good night.

"LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING=<postgresql://lakefs:lakefs@172.17.0.3:5432/postgres?sslmode=disable>"

@Guy Hardonag @Walter Johnson Should variable name be

LAKEFS_DATABASE_CONNECTION_STRING

instead of

LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING

(no POSTGRES in name) unless using version 0.80?

That’s right - for new installations with version >=v0.80.0 , the env var containing

POSTGRES

should be used

I have gotten into the container for a few seconds by making /app/wait-for hang. While in there I ran /app/lakefs run and I got this response ->

Failed to open KV store                       error="unknown driver: "

Hi @Walter Johnson, Nice progress. Try adding

LAKEFS_DATABASE_TYPE=postgres

above

LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING

One step closer to nirvana

FATAL  [2022-09-15T19:49:12Z]cmd/run.go:123 cmd/lakefs/cmd.glob..func8 Failed to open KV store                       error="connect failed: failed to connect to `host=/tmp user=lakefs database=`: dial error (dial unix /tmp/.s.PGSQL.5432: connect: no such file or directory)"

Happy to hear 😄 😄 Hope it goes smooth from now on. We are here if you need any help!

This inspired me to create my first npm package https://www.npmjs.com/package/lakefs

Cool 😒unglasses_lakefs: Will check it out Thanks!