Posted on 08-10-2016 06:57 AM
I have a number of Ubuntu Server VM's as my Casper distribution points serving via AFP and SMB on JSS 9.92
I also have Graham Gilbert's docker implemented BSDpy solution running for Netboot services on the VM's
https://grahamgilbert.com/blog/2015/04/22/getting-started-with-bsdpy-on-docker/
When I follow the instructions on this post to enable http downloads https://jamfnation.jamfsoftware.com/article.html?id=216
I get the following error
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
I know that one of my BSDpy docker instances is already using port 80
I'm wondering is this as simple as changing the port apache2 is using
Or should I change the docker port?
This has all come about from an idea to do a quick test on http downloads in my Self Service as I am having issues whereby the file sharing points sometimes take forever (over 5 minutes) to load when running a policy from the Self Service app. Seemingly randomly, but mostly when I am at a user's desk trying to show them how to use Self Service. That's actually my my issue and I haven't had any luck finding any mentions of a similar issue on here
Posted on 08-20-2016 03:24 PM
@O'Sullivan I'd change the Apache2 port.. NetBoot is a cranky thing.. so changing the port may just anger it.
Posted on 08-22-2016 12:48 AM
You will have two issues.
1) Docker is indeed using that port already, so you won't be able to re-use it.
2) All ports on Ubuntu below 1023 are marked by the OS as "privileged". This means there's extra work needed involving "authbind" if you want to run a daemonised server instance on your server running, say on port 443.
This is now getting into heavy system admin territory.