The ability to change the origin port in the config for Arc's Docker (currently it is set to port 8081)
We would like to have the ability to change the origin port in the config from port 8081 for Arc's Docker as sometimes this port is required by other software packages. In our case, port 8081 is needed for our company's McAfee's wake up agent.
The latest PageBuilder CLI 2.2.4 is now only exposing 80 (http), 27017 (mongodb) at the host machine. All other ports previously exposed are now became private within docker network between PageBuilder containers and don't try to map at the host machine when you start PageBuilder locally.
You previously mentioned 8081 which was mapped by PageBuilder that was conflicting with McAffee should now be resolved and both applications should run without conflict.
See release notes for PageBuilder CLI 2.2.4 in What's new in PageBuilder CLI page. Let us know how it goes in your development machine after upgrading the CLI to 2.2.4.
We have reviewed the effort and we'll plan this for future Engine release. It will require both Engine and Engine-CLI release to allow this capability.
Before we assess the change required for the hardcoded ports, can you check the following hardcoded ports for engine docker containers, if they also conflict with McAfee or other tools you are using: 8081 (McAfee), 8888, 9010, 9030, 9020, 9229
Hi Wayne,
The latest PageBuilder CLI 2.2.4 is now only exposing 80 (http), 27017 (mongodb) at the host machine. All other ports previously exposed are now became private within docker network between PageBuilder containers and don't try to map at the host machine when you start PageBuilder locally.
You previously mentioned 8081 which was mapped by PageBuilder that was conflicting with McAffee should now be resolved and both applications should run without conflict.
See release notes for PageBuilder CLI 2.2.4 in What's new in PageBuilder CLI page. Let us know how it goes in your development machine after upgrading the CLI to 2.2.4.
Hi Wayne,
We have reviewed the effort and we'll plan this for future Engine release. It will require both Engine and Engine-CLI release to allow this capability.
Hi Fatih,
We checked and the conflict is only with 8081.
Thanks,
Wayne
Hi Wayne,
Before we assess the change required for the hardcoded ports, can you check the following hardcoded ports for engine docker containers, if they also conflict with McAfee or other tools you are using:
8081 (McAfee), 8888, 9010, 9030, 9020, 9229