You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a similar (though not the same) issue, and managed to work around it. Here's what I found in my case:
The connection reset by peer is from docker-proxy. It happens because the fnserver container doesn't actually bind to a port inside its container.
My fnserver doesn't bind to a port because it is stuck before the startup procedure completes. If the startup did manage to complete, it would yield a message like Fn serving on :8080. You do have this message, but I do not. So your issue is probably with the point above.
In my case, the fnserver was stuck during startup because it failed to connect to docker. It tried connecting to the unix domain socket, even though my docker was configured to bind to tcp, and DOCKER_HOST was set. My workaround was to bind my docker to the unix domain socket instead.
Just in case someone else comes by from googling this issue as well :)
Description
fn create app myapp
Fn: Post "http://localhost:8080/v2/apps": read tcp [::1]:41904->[::1]:8080: read: connection reset by peer
Steps to reproduce the issue:
Notice in output-
time="2021-05-23T16:56:54Z" level=info msg="Fn serving on
:8080
" type=full version=0.3.749Describe the results you received:
Fn: Post "http://localhost:8080/v2/apps": read tcp [::1]:41904->[::1]:8080: read: connection reset by peer
Describe the results you expected:
myapp created
Additional information you deem important (e.g. issue happens only occasionally):
Output of
fn version
(CLI command):Additional environment details (OSX, Linux, flags, etc.):
Linux
The text was updated successfully, but these errors were encountered: