Error when deploying functions via Github Actions: failed to create task for container. about edge-runtime HOT 6 CLOSED

Hi @nyannyacha
I just got a message from the support team. They suggest that I turn off analytics in the config.toml file and try again. I haven't had a chance to try it yet but when I do I'll post the outcome here.

from edge-runtime.

Hi @nyannyacha
I have updated my config.toml file and disabled analytics and the job runs successfully via GitHub Actions.
Apparently GitHub Actions does not support the logging driver and hence was causing the error.

For reference:
config.toml

[analytics] enabled = false port = 54327 vector_port = 54328 backend = "postgres"

from edge-runtime.

Is there a way to only disable this in the Github Action run? I want to use the logging features in my localhost, but still deploy using github.

from edge-runtime.

@Silthus it looks like you can use environment variables in the config file: https://supabase.com/docs/guides/cli/managing-config#using-secrets-inside-configtoml

from edge-runtime.

Hi! @AdamMoroff75 😋

I can't talk much about this cause I'm not a member of the supabase team, but I don't think the runtime has caused that problem.

Runtime does not use the port 54328 you mentioned above by default unless you never set that port in the runtime manually.

Maybe the problem is related to @supabase/cli. AFAIK port 54328 is assigned for the vector image, which used in the analytics image to collect each container log.

Have you ever submitted this issue in @supabase/cli?

from edge-runtime.