Docker fix

[wardjm]

Sorry about taking this on so suddenly. I know you said someone else might be working it. This is all the initial changes required to build and run via docker.

[wardjm]

I should also comment to make sure to test your normal build process. I think everything was done in parallel with *_docker files (since the paths change), but may have accidentally messed something up unwittingly.

[GitHubProUser67]

Tada! We do! 65535 is (for now) used for the auto-IP negatiation, but I think... I will change it to be under 65532 anyway (the other port is trojan sensitive).

[wardjm]

Thanks! So it should be exposed for MitM? That comment reflected that only one of them can bind on that address/port pair, but all of the vcproj files listed it. So it just cannot be true that they all listen on the same port on the same computer.

[GitHubProUser67]

You are welcome!

Yes it should, but it is not an obligation.

This can be used by any server.

There is a lock system in place to make sure the port is not used twice at the same time.

And the listener will not remain on all the time, it only open the port and listen when needed.

[Jump-Suit]

As someone who uses MultiServer components dockerized, the edits to the existing dockerfiles do not satisfy docker image build conditions, as the other project references in the .csprojs are missing entries in the dockerfiles themselves.

Just to note, Right-Clicking in VS the project, and Add Docker Support to the project itself, will automatically adjust the dockerfiles to how they should be for compiling even if the files exist.

[wardjm]

As someone who uses MultiServer components dockerized, the edits to the existing dockerfiles do not satisfy docker image build conditions, as the other project references in the .csprojs are missing entries in the dockerfiles themselves.

Just to note, Right-Clicking in VS the project, and Add Docker Support to the project itself, will automatically adjust the dockerfiles to how they should be for compiling even if the files exist.

Thanks! I'd like to get this settled. Is it possible to say specifically what the problem is? Everything builds and runs, so I assume we are just missing a component or two. The entire source tree is copied over to the build images, so they don't have to be listed individually to be built there. Certainly this pull is way closer to correct than what currently exists.

[GitHubProUser67]

I think it now works without doing other project references because since, there is the deps fixer that modified the program startup net config file to take into account costura fody.

Is it possible to test it in a docker linux system?

[Jump-Suit]

I've built my Docker images directly on my backend via Portainer, if the dependencies aren't included in the dockerfiles, they won't be found and will be considered missing upon attempt to compile.

[GitHubProUser67]

Can you indicate how to do it?

I think this is worth the inclusion for wardjm but if you know how to do it and where to do it, it can save time I guess.