fn: [UX] registry URL without HTTP schema breaks registry URL parser

I was trying to (painfully) use serverless with fn from the quickstart, and while the deployment of the hello-world app is successful, I get an error 500 during the invocation. Trying to invoke from the web UI only yields the message “Something went terribly wrong (Status Code: 500)”

The problem with this is that while the failure counter is properly increased in the web UI, there is absolutely no log whatsoever:

$ fn calls l hello-world
$ fn logs g hello-world l
ERROR: No previous calls found.

I am at a loss trying to grasp how fn is emitting any log that would help me monitor and debug what’s going on now.

About this issue

  • Original URL
  • State: open
  • Created 6 years ago
  • Reactions: 1
  • Comments: 19 (13 by maintainers)

Most upvoted comments

Right, of course. I dropped fn start into a screen and detached it to let it run. I didn’t realize logs would then only be accessible from this console.

this is a type of error that happens before an actual function call, so, it gets resolved to http 500, but i do agree that it’s not user-friendly.

Interestingly, 10.12.1.2:5000 is my local docker registry. In fact, it’s right in the “image” column of doing fn routes l hello-world

Unfortunately, it seems it doesn’t work properly, was able to reproduce your error. As a way to fix your problem fast, make your docker talk to your registry and Fn will talk to your docker, so Fn wouldn’t need to talk to your registry. I’ll open an issue for this case.