Supported tags and respective
Where to file issues:
the Source Mage Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
Docker images for Source Mage GNU/Linux
Source Mage (or SMGL in abbreviated form) is a source-based GNU/Linux distribution based on a sorcery metaphor of "casting" and "dispelling" programs, which we refer to as "spells", and a package manager called "Sorcery". Our packages are designed to allow the user to customize the package any way they want (custom CFLAGS, LDFLAGS,
./configure flags, etc.) as well as offering as many of the package options as possible to the user up-front (you will not need to know what options a package has or what optional dependencies it can use ahead of time). Source code is always downloaded from the publisher's website and rarely patched. SMGL also includes many advanced features such as self-healing and sub-dependencies.
All of our scripts are GPL'd and our package manager and packages are written in bash, so they are easy to learn and modify. Sorcery supports custom packages maintained by users, which can override default packages and will never be touched by updates.
These images are based on our chroot images. To use them, simply do the following:
$ docker run -it sourcemage
$ docker run -it sourcemage:0.62
- in order to get the full benefit of castfs you need additional flags (
--device /dev/fuse --cap-add SYS_ADMIN) for access to
/dev/fusedevice within a container, but you've been warned because there are security implications to granting such capabilities/privileges to the container; otherwise installwatch will be used
0.62indicates the grimoire version this image is based on, otherwise
latestwill be pulled
All contents released under the GNU Free Documentation License.
All Source Mage code released under the GNU General Public License 2.0 or greater.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.