Wrong app-config URL caused by Docker Desktop

[Nico-Connor-Personal]

I had an issue where whenever I would run frau-local-appresolver I would get the wrong app-config URL.

Inputting the displayed docker app-config URL into the Free-Range App Manager would give me a 404 error code for my free-range application. The FRA would work if I used my machine name as the hostname: http://{computer name}.desire2learn.d2l:3000/app/appconfig.json .

After some investigating I discovered that when Docker desktop startups, it binds a hostname to your wireless lan adapter wifi ipv4 address. For some reason, when I deleted docker desktop, it didn't clean the bindings it created.

frau-local-appresolver is hard coded to scan your windows C:\Windows\System32\drivers\etc\hosts file and grab the first hostname that is bound to your local network ip address (if a binding exist). Since a binding existed for the docker host name, it would grab the docker host name to display as a variable for the app-config value.

Since the company recently migrated off of Docker Desktop, would it be a good idea to add a Known-Issue to the Readme of this project to instruct users to manually clean residual configuration left over by docker desktop if they're having issues with their app-config URL ?

Furthermore, would it be worthwhile to investigate if it is still necessary to scan the windows host file to set the hostname for the app-config URL?

[dlockhart]

Hi @Nico-Connor -- thanks for the detailed investigation! Absolutely yeah, definitely feel free to add this to a "known issues" section in the README and/or to look into modifying the code slightly to better handle this case. As you know, FRAs are on their way out, so there isn't any active development planned for this library.