search

hasura / graphql-engine

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
https://hasura.io
Apache License 2.0
31.18k stars 2.77k forks source link

v3 engine-1 fails with 400 / Unexpected / OCI runtime #10539

Open ggadwa opened 2 months ago

ggadwa commented 2 months ago

Component

engine-1

What is the current behaviour?

With the docker compose, all the components compile and install and are running except:

dev-setup-1 : exited -- you can run this and it exits without error, so if it was meant to run once then it worked right engine-1: error -- "(HTTP code 400) unexpected - failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./bin/engine": stat ./bin/engine: no such file or directory: unknown"

What is the expected behaviour?

That I have a functioning h3 environment in docker.

How to reproduce the issue?

Setup:

Windows, docker desktop / WSL 2. Pull the hasura / graphql-engine (this is the complete repository, with v3 as a sub directory) Rust already installed (1.81)

Run:

Go to the repository /v3 directory set the required variables (as described in the v3 readme) note I am following the postgresql setup docs docker compose up

Note:

For some reason the high external port set for postgres (64001:5432) flakes on my box; as I don't need to reach it externally I just removed the 64001. As it's external I doubt this is the cause but need to note the single change I made to the compose yaml.

Screenshots or Screencast

n/a

Please provide any traces or logs that could help here.

Docker desktop and the console returns this notification:

(HTTP code 400) unexpected - failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./bin/engine": stat ./bin/engine: no such file or directory: unknown

There seems to be no other logs of any use; running it in a console just shows everything is ok and started messages until this ultimately fails. More than willing to help out with a debug version!

Any possible solutions/workarounds you're aware of?

None that I know of.

Keywords

v3 OCI engine-1

Odex64 commented 1 month ago

Same error here.

ggadwa commented 3 weeks ago

Tried this again with the newest code; I see you have updated and fixed the bad port (on windows) in the docker compose so thank you. Still same error, though, so this is an outstanding ticket for any of us trying to run v3 locally.

Want to note there's a problem with pulling the newest code, it's in test folders so it's not a big deal but I suspect there's errant spaces in your paths, these files fail to pull:

error: invalid path 'v3/crates/metadata-resolve/tests/failing/aggregate_boolean_expressions/object/count_distinct_bool_exp_missing /metadata.json' error: invalid path 'v3/crates/metadata-resolve/tests/failing/aggregate_boolean_expressions/object/count_distinct_bool_exp_missing /resolve_error.snap' error: invalid path 'v3/crates/metadata-resolve/tests/failing/aggregate_boolean_expressions/scalar/count_distinct_bool_exp_missing /metadata.json' error: invalid path 'v3/crates/metadata-resolve/tests/failing/aggregate_boolean_expressions/scalar/count_distinct_bool_exp_missing /resolve_error.snap'

Notice the spaces after "count_distinct_bool_exp_missing".