mattbucci/steam-runtime-docker

Dockerfile and build scripts for using https://github.com/ValveSoftware/steam-runtime in Docker

steam-runtime-docker

Docker images with the 32-bit and 64-bit Linux runtime environments built by https://github.com/ValveSoftware/steam-runtime. These are intended to be used to make Linux builds for Steam games on a Windows host.

Note: I'm only using the GCC version myself, CLANG versions are untested

Sources Dockerfiles

• 32-bit (makes builds that run on anything that can run Steam)
• • jimbly/steamrt-precise-base - just barebones Ubuntu 12.04 sourced from the Steam repo
• • jimbly/steamrt-i386 - steamrt and build-essentials added in (used by all below)
• • jimbly/steamrt-i386-gcc GCC 4.8
• • jimbly/steamrt-i386-clang-3.4 CLANG 3.4
• • jimbly/steamrt-i386-clang-3.6 CLANG 3.6
• 64-bit (included for completeness, useful for tools)
• • jimbly/steamrt-precise-amd64-base - just barebones Ubuntu 12.04 sourced from the Steam repo
• • jimbly/steamrt-amd64 - steamrt and build-essentials added in (used by all below)
• • jimbly/steamrt-amd64-gcc GCC 4.8
• • jimbly/steamrt-amd64-clang-3.4 CLANG 3.4
• • jimbly/steamrt-amd64-clang-3.6 CLANG 3.6

Prerequisites - Windows

• Latest Docker not recommended because it breaks the ability to run any other VMs on your system :(, so, Docker Toolbox instead (though this should all be able to be made to work on vanilla Docker, the setup steps will be different)
• Install Docker Toolbox
• • If you already have Git/Bash and VirtualBox installed, you can skip those steps
• • • You'll probably need to fix the "Docker Quickstart Terminal" shortcut to point to where you have Git/Bash installed
• Linux host (or VM) only needed if you want to re-generate steamrt-precise-base

First, open the Docker Quickstart Terminal at least once for it to do initial setup.

Recommended: if you want to set the VM disk maximum size to more than the default 20GB (it auto-grows to this limit, it won't actually take 100gb if you set the max to 100gb), use the Docker Quickstart Terminal

• A steamrt image takes around 1.7GB, I easily used 20GB while debugging Docker containers, but only end up using about 5GB (including Docker's internal stuff) to just build the example Dockerfile
• WARNING: this will delete all existing Docker images and containers!
• docker-machine stop default
• docker-machine rm default
• docker-machine create -d virtualbox --virtualbox-disk-size "100000" default

Next need to set up the shares so processes in your Docker image can get at your files. I'm only running build processes (inherently trusted), so simply share my entire drive(s). Again using Docker Quickstart Terminal:

• docker-machine stop default
• In VirtualBox, for the VM named "default" go to Settings..., Shared Folders, add path of "C:" mapping to "C" (capital is important for easier scripting), Auto-mount
• docker-machine start default

Finally, to actually use these images, open your favorite terminal (or keep using the Docker Quickstart Terminal) and navigate to the example/ folder

• If not in bash: docker-machine env --shell=cmd default - get these variables into your environment via copy and paste or following the instructions - you'll need to do this in any automated scripts that make use of Docker.
• docker build -t steamrt-example . - only need to do this once, or when you make changes to example/Dockerfile
• docker run -it --rm -v /C/:/C steamrt-example bash
• You should then be able to navigate to any folder, and starting doing builds. Any changes you make (outside of to /C, which is simply mounted) are discarded when you exit your session, if you want to make configuration changes, edit Dockerfile and re-build the image.
• To build something non-interactively from Windows, (e.g. in a Visual Studio build step):
• • docker run -i --rm -v /C/:/C steamrt-example bash -c "mkdir -p /C/SRC/MyProject/build/ && cd /C/SRC/MyProject/build && cmake .. && make"