#Cloud66 Deployment

1 messages · Page 1 of 1 (latest)

native sparrow
#

Hi @void anchor, thanks for sharing can you give us more details about your configuration and running options ?

void anchor
#

Sure

#

Heres the Cloud66 yaml:

# 
---
ports:
- container: 3476
  http: 3476
- container: 3478
  http: 3478
volumes: []
traffic_matches: []
command: serve
#

so you can see theres nothing special

#

Im using the latest image: ghcr.io/permify/permify:latest

#

Ive also tried ./serve

trim pewter
#

Hi @void anchor , when pulling an image, using the "latest" tag may sometimes give you an older version. To ensure that you get the correct version, Can you use this ghcr.io/permify/permify:v0.3.0

void anchor
#

Ok

#

Same error 😞

#

Is it possible theres something wrong with the permissions for the executable or path in Docker/Kubernetes?

#

Ok, upon looking further, it seems like its more of a container issue than specific to the permify command

#

it fails whenever I try to put in any command with the same error

#

Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "sleep": executable file not found in $PATH": unknown

trim pewter
#

I don't think that because we have tested many cloud services, but we have not yet tried Cloud66. I'll take a look at its specifications and get back to you with more information soon

void anchor
#

Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"sleep\": executable file not found in $PATH": unknown

#

Ok, let me know if you need me to test or try anything else

trim pewter
#

Which cloud provider are you using in Cloud66?

void anchor
#

Azure

native sparrow
fresh jackal
#

Hi @void anchor is it possible that command here is actually the ENTRYPOINT in terms of Dockerfile context? So instead of a command you could give an argument. I am not really familiar with Cloud66 so I could be wrong here.

void anchor
#

@fresh jackal Interesting... it does appear to be an issue with the Entrypoint

#

changing to permify serve instead of serve seemed to fix it

void anchor
#

@native sparrow so, we are running into another issue with Permify with Docker on Cloud66

#

when using gRPC, we get the following error on any request

# 
  path: '/base.v1.Relationship/Write',
  code: 13,
  details: 'Received RST_STREAM with code 2 (Internal server error)'
#

It seems possible it might be a SSL/TLS issue, with the nginx proxy

#

We have set up the certificate on nginx, as well as specified the cert path

#

One thing that is interesting is that I cant even use the list command to reflect on the avaliable service/methods

#

Failed to list services: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: PROTOCOL_ERROR

void anchor
#

Ok, figured it out.