When trying to upgrade from fleet 3.4 to 3.6 im seeing permission denied logs from the fleet container when trying to open 443 for the web ui
Noah Talerman
1 year ago
Hi, do you mind posting the log output you’re seeing in this thread?
w
wkleinhenz
1 year ago
surethese come following start up
zwass
1 year ago
Were you binding to port 443 when using previous versions of Fleet?
w
wkleinhenz
1 year ago
yeah just with the normal docker compose portsis it happening cause its trying to open a port under the like the 1024 protected ports, cause the container isnt being run as root
zwass
1 year ago
Oh, yeah, actually this is probably because we stopped using
root
as the user in the container. Can you bind to a higher port in the container and then map it to 443 on the host?
