Difference between revisions of "How To Use Docker Toolbox With MPB"

From MOD Wiki
Jump to navigation Jump to search
(-p 9000:9000)
(add advanced)
Line 25: Line 25:
 
* The image size is around 1Gb, split across several files.
 
* The image size is around 1Gb, split across several files.
 
* The previous commands will create a new docker environment every time you run them. You only need them once.
 
* The previous commands will create a new docker environment every time you run them. You only need them once.
 +
 +
 +
After you close the console window, you can resume where you left off by running:
 +
 +
<source lang="console">
 +
$ docker start -i mpb
 +
</source>
 +
 +
 +
== Docker Advanced ==
 +
 +
If you don't want to use a pre-compiled image, you can build mod-plugin-builder yourself.
 +
To begin, start docker and run:
 +
 +
<source lang="console">
 +
$ docker run --rm -ti --name mpb -p 9000:9000 -v /path/to/docker/files:/tmp/mbs mpb
 +
$ exit
 +
</source>
  
  

Revision as of 09:54, 18 August 2016

Introduction

This is a quick start guide to get the mod-plugin-plugin working inside docker, running in Windows or MacOS.

We'll be using Docker Toolbox for this.
So before we begin please install that first.

Docker Basics

After you install and run docker toolbox you should be presented with a command-line interface.
This console is actually running Linux inside a virtual machine, but without you having to do any configuration or setup.

To begin, we download the pre-compiled mod-plugin-builder docker image by running:

$ docker run -ti --name mpb -p 9000:9000 moddevices/mod-plugin-builder

If you wish to have a local folder accessible inside the docker environment, use the '-v' argument with the local and docker mapped folder joined by a semi-colon. Like this:

$ docker run -ti --name mpb -p 9000:9000 -v ~/local-mod-folder:/tmp/local-mod-folder moddevices/mod-plugin-builder

Some notes:

  • The image size is around 1Gb, split across several files.
  • The previous commands will create a new docker environment every time you run them. You only need them once.


After you close the console window, you can resume where you left off by running:

$ docker start -i mpb


Docker Advanced

If you don't want to use a pre-compiled image, you can build mod-plugin-builder yourself. To begin, start docker and run:

$ docker run --rm -ti --name mpb -p 9000:9000 -v /path/to/docker/files:/tmp/mbs mpb
$ exit


After you close the console window, you can resume where you left off by running:

$ docker start -i mpb


You can find more information about docker here.