cli icon indicating copy to clipboard operation
cli copied to clipboard

When starting Fn on a different port the console still shows 8080

Open sachin-pikle opened this issue 7 years ago • 4 comments

I used fn start -p 8081 and my Fn server started successfully on port 8081. However the console still shows port 8080.

..... time="2018-05-10T11:32:49Z" level=info msg="Fn serving on :8080" type=full

Versions used: Client version: 0.4.87 Server version: 0.3.439

sachin-pikle avatar May 10 '18 12:05 sachin-pikle

@sachin-pikle i guess you are taking this wrong. You have two ports: the one docker exposes and the one that container expose. So, that's said, when you use -p <port> you expose container with the following port binding: <your-port>:8080. If you want to change Fn's port: use --env-file

denismakogon avatar May 10 '18 12:05 denismakogon

Yes I see what you mean. But it's confusing, at first .. Anyway this is really a low priority issue.

sachin-pikle avatar May 10 '18 17:05 sachin-pikle

It’s not an issue. In logs you see what you pass in Fn configuration, but not what you pass with -p

denismakogon avatar May 10 '18 17:05 denismakogon

May this issue be closed?

josephholsten avatar Sep 18 '18 23:09 josephholsten