[VS6] add Dockerfile and docker-compose to build the code

[PiecePaperCode]

Added two dockerfiles

Dockerfile & docker-compose.yml

With this two files you can locally build your copy of the source code. The binarys are dropped down on your build directory ./build/docker

No dependency needed to be installed on the development machine only docker

[tintinhamans]

I don't know how I feel about having a dependency on master branch of a repo outside of our control.

[PiecePaperCode]

can we inhouse vs6 in TheSuperHackers as a repo. Otherwise you need to hund it from an outside repo.
itsmattkc is a youtuber i follow an wich i trust to not have tempered with the distribution of vs6. Maby a trusted member can source the vs6 files and provide them in a repo.

[xezon]

No idea about the nature of VS6 redistributability. @OmniBlade @Generalcamo thoughts?

Locally I am using the VS6 SP6 package that OmniBlade has put together.

[tintinhamans]

No idea about the nature of VS6 redistributability. @OmniBlade @Generalcamo thoughts?

Locally I am using the VS6 SP6 package that OmniBlade has put together.

Perhaps we can think about making this a mandatory mount that the user provides, that way it is not redistributed inside of the image.

[Generalcamo]

Agreed with @tintinhamans, I am uncomfortable with distributing this.

[PiecePaperCode]

I have optimized the image.
The current size is now 2.8G. From 5G
The biggest culprit for the size is wine.
I generate the wineprefix on the fly.
This ads another 2G to the runtime instead inside the image

[tintinhamans]

Actually, why not expand on this entire idea and implement devcontainers?

They are supported in many IDEs: VS, VSCode and more.

[PiecePaperCode]

Actually, why not expand on this entire idea and implement devcontainers?

They are supported in many IDEs: VS, VSCode and more.

Yeah dev containers are a interesting approach but for this PR its out of scope.
Devcontainers should be in its own PR or/and a new issue.