Dolmades v1.2 - "Soap-free Cleanser"
Dolmades are intended as a mean to ease packaging, installation, usage and distribution of Windows applications in Linux environments to the utmost extent. A dolma is a containerized Windows app which runs on Linux without external dependencies.
- Installation: build your application using recipes and create a desktop symlink and menu entry
- Target launcher: choose between installed binaries which one to run
- Shares: bind selected paths from the host system to internal Windows drives
- Import and Export: share your applications across Linux systems
- Create recipes: use the existing recipes as template and derive your own for a specific Windows apps
- Create installers: distribute your dolmades as standalone installers
- Debug mode: examine problems, add fixes and instantly rebuild the app
- Selectable base: choose between several Wine versions
- GOG gaming support: generate template recipes for your personal GOG collection
The focus of the v1.x release cycle will be put on support for latest vanilla wine stable and staging, the standardization of the recipe specification used to create dolmades, proper ingredients handling, the protoypical implementation of the basic concepts and the completion of major unresolved issues.
- Ease of use: standalone installable on major Linux distros while requiring no special permissions
- Compatibility: recipes create functional dolmades across various distros and system hardware
- Mobility: designehttps://github.com/id to be executable across various distros and system hardware
- Safety: isolated from each other and from the host system by default to prevent data loss
The current prototypical implementation is done in form of the following Python scripts:
dolmades- to maintain your installed windows applications
cook- cooks a dolma given a recipe and its ingredients
box- creates a standalone installer from a cooked dolma
goglizer- creates template recipes for win-only GOG games; GOG account required
config.py- a configuration file providing important settings
Once the prototype is feature-complete I want to work on an enhanced version based on Qt and a remote repository service where user can store their dolmades, ingredients and recipes.
- x86 Linux (32 or 64 bit) with X.Org and XDG-compliant desktop environment
- Python 2.7
Dolmades make use of the following underlying technologies:
- Docker + DockerHub: for the dolmades base images
- udocker + proot: for user-level containerization
- wine: for running windows application in Linux
- winetricks: for installing most common ingredients
- lgogdownloader: for GOG support
- makeself: for creating standalone installers
- Possibility to define file/directory/device binds in recipes
- Create boxed dolmas as offline standalone installable
- Fixes for singularity, and if installed dolmas do not use it by default any longer
- Updated docs and lots of bug fixes
v1.2 "Soap-free Cleanser"
- Wine 4.0.2 / 4.20
- Refactored docker base images: winehq-stable-xenial, winehq-stable-bionic, winehq-staging-bionic
- Code cleanup / bug fixing / beautification
- Fix broken menu entry deinstallation
v1.1 "From Blue To Green"
- Support creation of self-installable dolmades
- Import&Export working reliably now even when user name changes
- Support for 32 bit kernels
- Improved recipe specification
- Improved ingredients handling
- Lots of refactoring / bug fixing
- Beautification (concept, textual output, code)
- Improved documentation
- Updated base images to Wine 4
v1.0 "The Goglizer" - 2018-11-27
- Initial release
Dolmades makes use of several concepts which will be briefly explained here:
- Dolmades: Win apps which behave like containers. They can be created, configured, executed and migrated.
- Recipes: Specification files similar to Dockerfiles which define the building process of a dolmade.
- Ingredients: Recipes require certain ingredients which can be ISO files, installers, media files ...
- Binds: Files contained in dolmades are isolated by default but access to files or directories on the host system can be configured using shared binds
Either download the release tar ball
curl -L -o dolmades.tgz https://github.com/dolmades/dolmades-cli/archive/v1.2.tar.gz tar -xzf dolmades.tgz cd dolmades-cli-1.2/
or simply clone it using git:
git clone -b "v1.2" --single-branch --depth 1 https://github.com/dolmades/dolmades-cli.git cd dolmades-cli
Cooking a dolmade
Cooking describes the process of building a dolma from a recipe given its required ingredients. To cook a dolma use the very simple example:
This will install the winning demo of Assembly 2007 by Andromeda Software Development. At first the required ingredients will be downloaded and verified by its checksum. Next, the dolmade is created and the installation as defined in the recipe is being performed. Finally, you can run the installed dolmade:
./dolmades launch LifeForce_ASD
The dolma can now be uninstalled again:
./dolmades del LifeForce_ASD
Now a second example: the free (as in beer) adventure game "Broken Sword":
./cook recipes/Broken_Sword.dolma --serve
This will create the dolma and add menu entries and a desktop symbol.
./cook launch Broken_Sword
A launcher will appear and offer you multiple choices created by the installer.
Windowed Mode and click "Ok":
The game will be started. You should be hearing sound unless wine detects the wrong alsa device which still may happen on some hardware.
A system tray icon indicates the running dolmade. On left click you can access the run log, on right click you can forcibly terminate the running dolma in case it hangs. The dolma can be removed via the corresponding menu entry.
More recipes for dolmades can be downloaded here
Generating a GOG dolma
For this to work you'll need to be registered at GOG. They offer some items for free so you can actually test
goglizer without purchasing a game. If you have not done so already obtain the free item "Flight of the Amazon Queen" and verify that it is shown in your personal game collection. Retrieve a list of your games using the script
-u parameter tells
goglizer to retrieve the dolmades runtime container and your personal game list.
At first, you will be asked to authorize using your GOG account. Since two-factor-authentication is mandatory you will need to check your email and enter the code that GOG has sent to you. This needs to be done only once since the authorization credentials are being stored in your home directory for subsequent use.
Finally, a list of your games is displayed:
Found dolmades repo under /home/stefan/.dolmades/repo Pulling dolmades runtime container... da4bf27d-3bf2-3436-916a-e1bc83098523 done Fetching detailed info about games from GOG... Retrieving detailed linux game list... Getting game names (1/1) 48 / 48 Getting game info 26 / 26 Retrieving detailed linux/windows game list... Getting game names (1/1) 48 / 48 Getting game info 48 / 48 Retrieving detailed windows game list... Getting game names (1/1) 48 / 48 Getting game info 48 / 48 done! Windows games available on this account which have no linux installer available broken_sword_3__the_sleeping_dragon ... flight_of_the_amazon_queen ...
Note, that only games are listed that have no linux installer. If you want linux games to be listed as well you need to use the
./goglizer -l Found dolmades repo under /home/stefan/.dolmades/repo Windows games available on this account (bold: no linux installer available) akalabeth_world_of_doom beneath_a_steel_sky broken_sword_2__the_smoking_mirror broken_sword_3__the_sleeping_dragon ...
Now choose a game of your liking and instruct
goglizer to download the ingredients and create a corresponding recipe template using the
Now the dolma can be installed:
./cook "flight_of_the_amazon_queen:en:1.1.dolma" --serve
After successful completion you will find a clickable icon on your desktop and a menu entry :)
You can skip the
goglizer run completely by using the recipe under
As of now for one out of two games the installation procedure fails or the installed game won't work properly. If that happens dolmades makes it easy to find and apply fixes to the generated recipe. Let's give an real example:
We try to cook it:
The java installation will fail and leave a broken dolma. First, we need to figure out interactively what needs to be done:
./dolmades debug edna_harvey_the_breakout:en.dolma > # THIS IS THE REQUIRED FIX: set windows version to WinXP > winetricks winxp > # rerun installer and ensure that it works now > /install/setup_edna_and_harvey_the_breakout_184.108.40.206.exe # test cooked dolmade, start in windowed mode targetSelector
The previous changes are now applied permanently to the dolma but will get lost if it will be recooked.
That is why we ought to update the corresponing recipe to include that fix.
edna_harvey_the_breakout:en.dolma and add the following section right before the
RunUser command which launches the installer using
RunUser winetricks winxp
Finally, the dolma can be cooked once more:
This erases the previous dolma and helps keeping recipe and cooked dolma in sync with each other.
Once a dolma has been cooked and thoroughly tested it is possible to convert it into a standalone installer:
This will package all dependencies and create an offline installer script based on
makeself which installs on various Linux systems without special privileges.
The approximate size overhead produced by the Ubuntu Base Image and the wineprefix will be 800Mb.
Users who download this file should open a terminal at the location of the downloaded file and run the installer like this:
After accepting the license the dolma will be installed under
$HOME/Dolmades-v1.1/LifeForce_ASD. It can then be launched or removed again from the created menu entry or the desktop symbol.
Note: as of now self-installable dolmades will require Python 2.7 and curl on the host system. A future release will probably get rid of this requirement.
Your dolmades are managed by
Lists the locally available dolmades:
Removes the given dolma (data, menu entries and desktop symbols) and frees up the allocated space:
./dolmades del name-of-dolma
You can pass multiple dolma names or sha256 container ids.
/.dolmades/start.sh script which either runs the executable defined via
SetTarget in the
or the target selector script which lets you choose between all installed targets.
./dolmades launch name-of-dolma
It is possible to launch a bash inside the container.
The installation directory will be available under
/install and installed windows applications under
Furthermore, the home directory of the calling user is available:
./dolmades debug name-of-dolma ls -lad $HOME /wineprefix /install
In rare cases you might want to run as fake root, e.g. to install a missing package:
./dolmades root-debug runtime apt-get update && apt-get -y install vim
name-of-dolma is given as argument the changes are being applied permanently.
name-of-base is given as argument a temporary dolma is being created and destroyed after the shell is being closed.
name-of-base is used as template and currently can be one of the following:
runtime- used internally by
base- Ubuntu 18.04 LTS prepared for the installation of wine
basewith wine stable added and preconfigured
basewith wine testing added and preconfigured
It is possible to make files or directories of the host file system accessible from within the container by defining so-called binds. These will apply just when a dolma is being launched but not when it is being debugged. Usually it is sufficient to use the predefined default binds in the recipe.
./dolmades rebind name-of-dolma # reset the binds as defined in the recipe # this command is performed during the cooking procedure
./dolmades binds name-of-dolma # listing the currently configured binds
./dolmades bind name-of-dolma bind1 bind2 ...
A bind is defined using absolute path names as follows:
Use this way to set binds just for tests as they are temporary and will not persist when a dolma is being exported and imported subsequently.
Generally define the binds in your recipe where they will persist over imports/exports.
- In wine the C and the Z drive are predefined. Utilize
/wineprefix/drive_e:/my/hostdir/to bind to drive E.
config.pypredefines a certain set of binds which can be enabled by default. These will allocate some more driver letters starting from Y in reverse.
- The output of
dolmades exportwill not change depending on configured binds whereas the output of
config.pypredefines a certain set of binds which can be enabled by default
- It is possible to use
It is possible to export and import a readily installed dolmade.
./dolmades export Broken_Sword Broken_Sword.dme
./dolmades import Broken_Sword
The final goal is to be able to export the dolma on some linux system running under some hardware and import it on another linux system running another hardware. Since the user name will likely change all users home directories are shared and being symlinked to
root. Also, things can stop working if the hardware changes, e.g. sound stops working, but can be fixed easily by running
winecfg in debug mode.
Menu entries and desktop symbols
Last but not least the dolma can be served on the desktop
./dolmades serve name-of-dolmade
This will create a clickable icon on the desktop and a sub-menu entry which will launch the corresponding dolmade. In addition a menu entry for uninstallation is created. It is possible to remove the menu entries and the desktop symbol again without uninstalling the dolmade:
./dolmades clearaway name-of-dolmade
You should hardly need this command but better safe than sorry!
Initialization does two things:
- if it doesn't exist yet: initializing the dolmades directory under
- downloading the
dolmades-runtimecontainer with the matching version and (re)create it
dolmades pulls its base images from DockerHub. The Dockerfiles specifying the build and the build script are to be found in the
- winehq-stable-xenial - current wine stable version with mesa 18
- winehq-stable-bionic - current wine stable version with mesa 19
- winehq-staging-bionic - current wine staging version: development version + custom patches with mesa 19
As of dolmades 1.2 all immages are for 64-bit linux only. If you need a 32-bit image you can modify the Dockerfiles and easily build them yourself. These images for releases will be tagged accordingly and not being rebuilt in future. This is what all images have in common:
- Ubuntu LTS base with wine PPA
- Wine installation under
$WINEPREFIXwith 32-bit prefix
targetLauncherGUI script under
wget curl less vimfor convenience
The following environment variables are available in a dolma (these are example values):
DOLMADES_BUILDDATE=2019-11-20 DOLMADES_GECKOVERSION=2.47 DOLMADES_WINEVERSION=4.0.2 DOLMADES_WINEBRANCH=stable DOLMADES_VERSION=1.2 DOLMADES_UBUNTUVERSION=bionic DOLMADES_MONOVERSION=4.7.5 LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 WINEARCH=win32 WINEPREFIX=/wineprefix
It is possible to create custom docker images on DockerHub as base for recipes which e.g. offer legacy wine, pba or Proton support.
All available tools give help output:
./dolmades help ./dolmades help bind ./cook ./box ./goglizer -h
Dolmades ships with preconfigured settings in
config.py. These are the most important ones:
VERSION = "1.2.0"- this is the utilized version of dolmades. It derives the
MAJOR_VERSION = 1.2which serves as tag to be used for base docker images and it has to match the
VERSIONsetting in the Dolmafile. The syntax used in Dolmafiles is compatible across all versions sharing a common major versions.
DOLMADES_PATH = HOME + '/.dolmades-MAJOR_VERSION'- this is the base path where dolmades stores its runtime, base images, dolmades, meta data, icons and GOG games lists. Note: you could change this path, but this will affect which host directories you can bind. A bind is never allowed to contain
DOLMADES_PATHsince it would be a security issue!
A recipe is a specification which allows the guided build of the respective dolmade. Dolmafiles are for dolmades what Dockerfiles are for Docker except that dolmades are not necessarily built fully automated and hence require interaction if a graphical installer is being used.
The structure of a
# Arbitrary comment... COMMAND1 ARGUMENTS FURTHER ARGUMENTS ... COMMAND2 ARGUMENTS ...
This command is mandatory. It defines the name of the dolma used internally by
dolmades. Whitespaces are not allowed.
This name is going to be slightly converted and used in the desktop icon title.
This command is optional. It defines the tag of the base image pulled by the recipe, and has to match with the version reported by
cook. Advised to be omitted in development, such that no version checking takes place, and the
latest base image is being used.
This command is mandatory. It defines the DockerHub repository to be used. The tag of the image used is defined by
DESCRIPTION A description of the contents of this dolma
This command is optional. This description is stored inside the container and it is not being used yet.
INGREDIENT sha256 filename description http://remote1 ftp://remote2 file://local3 gog://remoteid ...
This command is repeatable and optional. For each ingredient used within the recipe one entry is needed.
The ingredient will be fetched from one of the locations defined and made available inside the container under
RUNUSER cmd1 && cmd2 && ... && cmdN
This command is repeatable and optional. This command will be launched as the calling user in a bash environment inside the dolmade. config.py:INST_PATH will be the target directory.
You can cascade multiple commands by
&& and they will be executed subsequently. The first failing command, however, will terminate the execution. If all commands succeed a final
wineserver --wait ensures the proper termination of all wine processes.
RUNROOT cmd1 && cmd2 && ... && cmdN
This command is repeatable and optional. This command will be launched as fake root in a bash environment inside the dolmade. config.py:INST_PATH will be the target directory.
You can cascade multiple commands by
&& and they will be executed subsequently. The first failing command however will termine the execution. Usually
RUNUSER should suffice but if you need to install some packages using
RUNROOT will be required.
This command is optional. If omitted the dolma will launch using the target launcher and allow the user to select one of all installed targets i.e. lnk-files created during the installation. Sometimes it is desirable to launch a specific executable and then this option can be used to set the exe-binary.
This command is optional. Sometimes if
TARGET is used it is neccessary to also specify arguments. This can be done using this command.
This command is optional. Sometimes it is necessary to set some environment variables for an executable. For instance it is possible to force DLL overrides or specific language settings.
This command is optional. Sometimes it is necessary to call
wine using a preceding command e.g.
taskset -c 0 wine in order to limit the execution to a single CPU. This can help fix race conditions.
This command is optional. It specifies the icon file to be used for the desktop symbol and the target launcher with absolute path and file name.
If an absolute path is ommitted the
/wineprefix/drive_c directories will be browsed and the first occurrence of the given icon file name will be used.
If the command is omitted or the given file name cannot be found it defaults to the dolma icon.
This command is optional. It is possible to make certain locations or devices of the host system available by keywords predefined in
These binds are kept as setting and will be preserved when a container is being boxed, exported and imported again.
Currently predefined binds are:
- There has to be an empty line in between subsequent commands
- Comments can be added as lines starting with
#. Comments cannot be appended to existing command lines.
- The order of the commands has to be obeyed until parsing has been refactored. This is planned for the next release.
INGREDIENT- and maybe some other commands - are likely to undergo slight changes until the next release
- Which distros have been tested? See this issue
- Will dolmades focus on a particular distribution? I develop under Linux Mint, so Ubuntu and Debian-based distros might be most compatible. I plan to keep compatibility to major distributions though.
- Why does the syntax for the recipes change? So that it can evolve! As of now the syntax may change for every version. This does not matter since dolmades recipes will work when the
VERSIONof the recipe matches the
dolmadesrun script. Exported dolmades will contain all scripts necessary to rebuild and rerun the dolmade.
- Will the syntax for the recipes be fixed anytime? Probably. But not in the prototypical implementation phase.
- How secure is the sandboxing? If singularity is installed it will be used after installation by default. This offers real chrooted environments. Otherwise proot is used as a fallback which is not really secure but relatively safe since it prevents accidental destruction of data on the host system.
- Will dolmades support ever MacOSX or Windows? Maybe. But not for the foreseeable future.
- Is it enough to lookup ingredients by SHA256? TODO
Dolmades currently are a prototypical implementation done in python. Once feature-complete I want to work on an enhanced version based on Qt combining a remote repository service. The primary goal will be to create a powerful GUI to setup, maintain and run Windows software under Linux.
I figure some exciting use cases which would become addressable as well, e.g.
- Automated deployment of windows software and complex development environments on large pools of computers
- Cloud-based GUI applications based on Linux and VNC
- Enhanced debugging and development for wine development
- Fully automated dolma cooking using Xvfb / AutoHotKey
- Functional archival of legacy software
- Support for complex Linux software setups
udockerrequires Python 2.7 and will hopefully receive Python 3 support soon: https://github.com/indigo-dc/udocker/issues/77
udockerrequires tar with support of
-delay-directory-restore(see https://github.com/indigo-dc/udocker/pull/137) which every recent distro should provide
dolmadeswill be written to support Python 2.7 and bearing in mind Python 3 compatibility for later when udocker starts supporting it, too.
- wine does not work well with pure x86-64 software which is why the installed windows software actually needs to be compatible with 32-bit windows
- do not report issues to wine directly when
winetrickshas been used in the recipe
udockerfails to pull some layers from the docker registry (timeouts) - simply repeating the commands should help.
- GOG installer errors: many GOG games display error messages at the end of the installation process. I suspect some failing installer script commands are the source. The installed games seem to work anyways! According to this post these messages even occur on Windows machines!
Last but not least: if you are in trouble, check out the issues and open a new one if applicable.