i am trying to register flow with server deployed on gke and docker for flow storage, and getting belw mentioned error for Dockerfile

Where is the Dockerfile? the folder above?

yes

But it is a relative path (which means it is relative to the directory you’re in when performing registration). Are you calling this from the flows directory?

no one above flow directory where dockerfile is placed

That's what's causing the error then. It is looking for a Dockerfile one folder above the one from which you are calling the register cmd

Yeah Matthias is right I just tested the relative path calling from the directory below and it worked.

Indeed, if you

cd

into the flows dir and rerun the cmd it should be fine

exactly it worked but now faced another error when ran it from inside flow directory

That just says you can’t log in. How did you authenticate to Cloud?

gcloud

No that’s the Prefect log. Are you on Server or Cloud?

server

Then I think you didn’t do

prefect backend server

in the place you are registering from

did this but still getting the error

Can you show me the output of

prefect diagnostics

in the CLI?

Were you ever on Cloud? I am wondering if it’s still picking up a token you may have

yes i once was

I am wondering if your backend is server but your host/endpoint is configured to hit Prefect Cloud? Can you show me the

config.toml

? Or you do you use env variables? Just redact sensitive information

i have configured config.toml to point to apollo server as mentioned in this video

Ah ok so you think it’s configured right? can you register a dummy flow into the new project without Docker storage?

how?

Just remove the storage and register?

with Flow(...) as flow:
    ...

and then

prefect register …

?

yeah it did register

Wait you registered with the Docker storage? For stuck in scheduled look at labels

no i registered without docker storage as you said and it worked but with docker storage i was getting error as mentioend aboved

I am pretty confused why this would fail but local would succeed cuz they hit the same code path. What is in your Dockerfile? Do you have something there that interacts with the Prefect API?

i did not run it locally yes i register the flow with server but after removing the docker storage option like this with Flow(...) as flow: ... but when i used docker-storage option it does not register the flow but throws error

I honestly have no idea. It’s weird since you did manage to do all that before, we went through this entire process last year. Maybe try creating a new virtual environment and reinstall prefect there

no its not that one this time i am using server not cloud and docker as storage for my flow not github

maybe you can create your environment from scratch and switch the backend to server and check again?

Maybe try adding commands to switch to server inside your container

@Aqib Fayyaz if you didn’t manage to fix it until now, can you share the exact steps that you have taken so far to set it all up? What code did generate the exception you shared? If you can share a step by step approach you followed, we may try to reproduce the issue and see what is the root cause of it, but right now we don’t have enough information to say anything

Oh it worked the issue was because of sudo command. In my local system i was unable to run any docker command without sudo and that sudo caused reference to cloud instead of server so i changed the settings of my environment so that i can run docker commands without sudo and than i registered the flow without sudo and it worked it registered the flow. Thank you so much @Kevin Kho and @Anna Geller