Make docker run locally

[TracerDS]

This PR localizes Docker. It no longer copies mtasa repo but local copy of the mta.

[TheNormalnij]

You should use -v parameter in docker run to mount these folders into a container

[TracerDS]

How would it work?

[TheNormalnij]

You should mount mta repository (or an empty folder) to /build folder in a container. docker-entrypoint.sh runs inside this folder.

[TheNormalnij]

Why? Nothing is wrong here. This line allows you to build MTA without cloning the MTA repository.

[TracerDS]

this line actually clones the entire repo all the time.

[TheNormalnij]

It doesn't. Check your command line and current folder

[TracerDS]

It does. Docker pulls mta repo from github if that line is saved. Without it, it runs only local changes

[TheNormalnij]

No. I tested it

[TracerDS]

Me too. It didnt accept local copy unless I remove that line.
If you try to build mta then you already have necessary files in your filesystem.

[TheNormalnij]

cd <mta sa repo here>
docker build -t mtasabuilder:latest .
docker run --rm -v ./:/build mtasabuilder:latest

Does it work?

[TracerDS]

"volume name is too short, names should be at least two alphanumeric characters."

[TheNormalnij]

docker run --rm -v <full path to repo>:/build mtasabuilder:latest

?

[TheNormalnij]

It works locally now

docker build -t mtasabuilder:latest .
docker run --rm -v ./:/build mtasabuilder:latest

[botder]

Did you ever try the steps under Building with Docker from the README?

mtasa-blue/README.md

Lines 113 to 122 in 550a152

	**Building with Docker**
	These examples assume that your current directory is the mtasa-blue checkout directory. You should also know that `/build` is the code directory required by our Docker images inside the container. If the current directory is not a valid git repository, it instead create a (shallow) clone of the mtasa-blue repository. After compiling, you will find the resulting binaries in `./Bin`. To build the unoptimised debug build, add `-e BUILD_CONFIG=debug` to the docker run arguments.
	| Architecture | Build command |
	| ------------ | -------------------------------------------------------------------------------------- |
	| x86_64 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:latest ``` |
	| x86 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:i386 ``` |
	| arm | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:armhf ``` |
	| arm64 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:arm64 ``` |

[TracerDS]

Did you ever try the steps under Building with Docker from the README?

mtasa-blue/README.md

Lines 113 to 122 in 550a152

	**Building with Docker**
	These examples assume that your current directory is the mtasa-blue checkout directory. You should also know that `/build` is the code directory required by our Docker images inside the container. If the current directory is not a valid git repository, it instead create a (shallow) clone of the mtasa-blue repository. After compiling, you will find the resulting binaries in `./Bin`. To build the unoptimised debug build, add `-e BUILD_CONFIG=debug` to the docker run arguments.
	| Architecture | Build command |
	| ------------ | -------------------------------------------------------------------------------------- |
	| x86_64 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:latest ``` |
	| x86 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:i386 ``` |
	| arm | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:armhf ``` |
	| arm64 | ``` docker run --rm -v `pwd`:/build ghcr.io/multitheftauto/mtasa-blue-build:arm64 ``` |

I did, but no matter what I do I always get a copy of the github repo instead of my local one.

[botder]

I did, but no matter what I do I always get a copy of the github repo instead of my local one.

Alright, but did you try using --entrypoint /bin/bash to look around and see if you properly mounted the files in /build ?

[TheNormalnij]

"volume name is too short, names should be at least two alphanumeric characters."

Do you use powershell in windows?

[TracerDS]

Alright, but did you try using --entrypoint /bin/bash to look around and see if you properly mounted the files in /build ?

Didn't try that exact method but when lsing the root dir, no directories were copied.

Do you use powershell in windows?

Nope

[botder]

Alright, but did you try using --entrypoint /bin/bash to look around and see if you properly mounted the files in /build ?

Didn't try that exact method but when lsing the root dir, no directories were copied.

You're supposed to mount your local directory into the Docker container, and by poking around within a /bin/bash shell, you can see if your mount is actually working. If it's not there, then obviously the docker-entrypoint.sh script is going to clone the repository everytime.

[TheNormalnij]

Invalid / a system issue