Using Docker to produce AppImages


In order to create an AppImage compatible with a wide range of GNU/Linux systems the developer must choose as build base the oldest LTS system available in the market (which is Centos 6 at the time of writing this post). Why?

An AppImage package is a trade off between size and compatibility where some system libraries are left outside the package for different reasons: glibc doesn’t get well with older or newer versions of itself so if a given application tries to interact with another and they use different versions of glibc a crash is expected. Next time you found a glibc developer please ask them to respect backward and forward compatibility. Other situation is the case of libssl, if embed into the AppImage it may not receive updates and your app could end exposing your network traffic due and old bug.

In resume not all dependencies are bundled but those that are not expected to be present by default in your target systems. So if our application is built over old enough base libs and the libs developers were nice at keeping forward compatibility is guaranteed that your final bundle will run in all the systems with core libraries newer than the ones used tho build the product.

The problem

Sound easy, right? It’s just a matter to build your app on Centos 6 and we are good to go. I’m sorry to tell you that provably there will be no binaries of your dependencies available for Centos 6 and you will have to build it manually and you will also have to deal with weird toolchains to get gcc-7 on it. But don’t despair we are here to help.

The AppImageCarfters initiative aims to be a community driven effort to ease AppImage production. By creating ready to use recipes and binaries of common dependencies and toolchains we want to reduce the work of creating an AppImage to just setting up your app build script and sharing the effort of building dependencies.

In a previous post we show how to conan could help in this task now is time to give a chance to Docker. As a containerization solution it allow us to create a whole system independent from the one started on your machine with really low overheat. So we can create common base system with all requirements to ensure the major compatibility of the produced AppImages, the tools too do it and the common dependencies like frameworks.

And that’s exactly what is apppimagecrafters/docker-linuxdeploy. It gives you a build system with gcc-7, glib-2.44.0, autotools-1.16.1, autoconf-2.69 and cmake-3.15.4 all ready to be used.


Here is an example gitlab-ci script of how it could be used to build an AppImage from a HelloWorld C++-11 application:

  image: appimagecrafters/docker-linuxdeploy
    - cmake -DCMAKE_INSTALL_PREFIX=/usr
    - DESTDIR=AppDir make install
    - linuxdeploy --appdir=AppDir --output appimage --desktop-file=AppDir/usr/share/applications/net.azubieta.cpp_appimage_template.desktop

Looks great, right? Goodbye to hacks and hello to smooth AppImage creation.

I wonder if it could be simpler than that?

Notice that the application built above is a full desktop app that installs its own desktop entry and icon, which are mandatory requirements for building an AppImage.

Missing dependencies

If one of your dependencies is not in the AppImageCrafters repo you can create a Docker recipe using appimagecrafters/docker-base as base system. Make sure it gets installed into /usr/local by setting it as install prefix. Finally in your target build image use the COPY Docker instruction like this:

COPY --from=me/my-custom-built-library /usr/local /usr/local

You will get all the binaries built on me/my-custom-built-library into your system and as they were built over the same base system there will be no compatibility issues.


If you already distribute your app as an AppImage we encourage you to submit the recipes of your dependencies to the project so every one can benefit from them and also contribute.

Are you a Docker expert?. Well, we don’t, so we will love to hear how the recipes can be improved.

Use it, leave your impressions and spread the word. That would be terrific!


Creating Docker build images for AppImage is a practice long used to build the tools in the AppImageProject and the recipes found on the AppImageCrafters projects were inspired from the ones used by them.

Useful links:

  • AppImageCrafters org:
  • Docker repositories:
  • Example Hello World project:

Introducing AppImage Services


The AppImage project seeks to introduce into the GNU/Linux ecosystem to the best aspects of a MacOS app installation experience, while avoiding its drawbacks. But it faces the fact that there are many GNU/Linux Desktop Environments. Each one with different goal and opinion on how applications should be handled. Trying to satisfy all of their requirements and restrictions seems to be a nearly impossible task.

A desktop environment is conformed by a set of different software components such as file manager, applications launcher, software centers and others. All of them interact in a different way with applications and this interaction is ruled by the FreeDesktop specifications (whether DE respect it or not is another topic). AppImage as single file applications implies a new way of managing applications that need to be fitted into the existent standards. This “way” must be consistent between the different tools.

Therefore arises the need for an unified implementation of “the AppImage way” (TM). Which summarizes to: applications packed as single files with icons, metadata, applications launcher integration, mime types integration and updates support. All of that available from the different desktop environment components.

AppImage Services description

This tool should provide a API that could be used without restriction by every existent desktop environment. As there are many and each one uses different technologies we can only rely on using a IPC technique being DBus our best candidate as it's stable, tested and broadly adopted.

Each set of features will be exposed in a separated interface (like a micro-service) so the different clients applications doesn’t have to depend/implement and support a large API. Being the most relevant interfaces:

  • Launcher: responsible for creating launcher entries and of course launch appimage files
  • Updater: responsible for looking for updates and actually doing the update
  • Inspector: responsible for reading applications metadata and contents
  • Registry: responsible for keeping track of the applications in the system and the files they deploy

This solution should be packed in a self installable AppImage so no matter the target system it could be installed and consumed. This represent our biggest source of uncertainty as it steeps away from the traditional package managers.

Summarizing, AppImage Services is a set of DBus services for managing AppImage files in a FreeDesktop standards compatible way presented as a self installable AppImage.

The AppImage Services code can be found at binaries are available at


To install AppImage Services you will need a modern GNU/Linux system (>= Ubuntu 16.04) with systemd. Upstart version still not available but contributions are welcome.

wget -O appimage-service.AppImage
chmod +x appimage-service.AppImage
# user only install
./appimage-service.AppImage self-install

# system wide install
sudo ./appimage-service.AppImage self-install

Example QtWidgetsApplication packed as AppImage using


In a previous post was mentioned how well and AppImage could work in order to ease the production and distribution of your software. In this post, we show a minimal example of how to pack a Qt Widgets Application as an AppImage using as a dependencies management system.

What’s Conan? it’s a decentralized package manager. That allows us to have binaries ready to be used to create AppImages.

Why do you need such special binaries? In order to create an application that could be run on almost any GNU/Linux distribution you will need to build your application and it’s dependencies on a very old base system (by example Centos 6). So you will have to back-port every dependency to such system. Using our repository you can access to a wide range of package recipes that are ready to be built/used on almost any distribution. Such packages are available on bintray and the recipes are on github You will find them as part of the appimage-conan-community which is a group for those using this technology stack.

The Code

Let’s take a minimal Qt Widgets applications which uses qmake as build system. Then we will add a desktop file and an icon. Finally, we will declare our project dependencies using a conanfile.txt.


# linuxdeploy is required to build the AppImage therefore is listed only as build require

# allow to run qmake from the build dir
# create conan virtual environment (required to run linuxdeploy)

# Require shared libs

Now we can proceed building our AppImage:

mkdir build && cd build;

# Install conan dependencies requiring them to be built using c++ 11 and linked to libstdc++11  
conan install .. -s compiler.cppstd=11 -s compiler.libcxx=libstdc++11 --build missing

# Enter conan virtual environment (just like python virtual environments)

# build your app as your are used to
qmake CONFIG+=release PREFIX=/usr ../

# Let's crete the AppImage
# install you app to an AppDir
INSTALL_ROOT=$BUILD_DIR/AppDir make install

# call linuxdeploy with the Qt plugin
linuxdeploy --appdir AppDir/ --plugin qt --output appimage

# exit conan virtual env

You can find the whole project code on Github.

Please fell free to leave your comments below and enjoy hacking!


AppImage dependencies management


Currently the process of producing AppImages is hindered by the burden of making the whole dependency tree relocatable and compatible at binary level with older software. A crowd-sourced repository of binaries could be used to share and reduce this work. Several binaries repositories technologies were analyzed finding Conan as the best match for the AppImage project needs. It address the same issues with binaries, opens a wide range of options for future integration between both projects and also improvements for the AppImage project.


The AppImage format allows to create a single package compatible with a wide range of GNU/Linux distributions. To achieve this the developer must ensure that all the binaries inside the package are relocatable and the binary compatibility of the package external dependencies.

In GNU/Linux is quite common to find software that relies on fixed paths to resolve its resources. This must be fixed (usually by means of a patch) before using it as part of an AppImage package. Creating and maintaining such patches becomes an extra job for the application developer.

Binaries compatibility is a more complicated issue. It’s recommended that AppImage packages should have as few dependencies as possible. Only being considered as accepted dependencies: “glib”, “libstdc”, “libstdc++” and others (listed in the black-list). But even those highly common and well maintained libraries are infamous by continuous ABI breaks (specially “glib”). Usually there are workarounds for such issues but they need to be carefully applied to the whole application dependencies tree. Which is also more work for the developer.

In resume the current process of creating an AppImage puts into the developer the burden of creating/maintaining a whole set of patches and obscure workarounds for each one of the application dependencies. Notice that in some cases library developers are kind enough to create good (relocatable and backward compatible) binaries.

Problem: How to reduce the development and maintenance work associated to creating relocatable and backward compatible binaries as part of the AppImage production process?

Hypothesis: Having a crowd-sourced repository of relocatable and backward compatible binaries will reduce the overall maintenance effort as it will be shared between all the community members.

Dependencies management systems

Binary repositories is not a new idea at all so we must consider the technologies that already exists.

  1. Traditional GNU/Linux repositories

    Traditional repositories have been around for a while and have been improved a lot. Now maintaining a deb, rpm or Arch pkgs repository is not “too” complicated. So we could have a repository of sources/binaries which meet the requirements to be embed into AppImages. The sources can be hosted on Github or Gitlab where potential developers can contribute.

    Packages will need to be created with a different prefix so they will not crash with the system packages. Developers will have to properly setup this new prefix in their build environment manually. The rest would be regular app development.


    • Established, tested and documented technologies
    • Development workflow will change little from what people are use to


    • repositories are tight to a given distribution.
    • annoying packaging rules
    • almost every package would have to be redefined/rebuilt on a old enough system
  2. Snappy

    Parts is the name Snapcraft gives to dependencies. As the final apps binaries they are built against a common base system (snap-os) which should be present in every target system altogether with the dependencies resolution app: snappy. It would be possible to mix into a single AppImage the required sections of snap-os and all the dependencies. Additionally will be required to remove non-required files that could be part of a given package but are not used by the final application.

    Existent snap packages recipes could be used to produce AppImages. But they will need to be rebuilt and stored somewhere. Maybe in the Snappy Store or in a custom store. Developers will need to snappy install them and the snapd daemon should take care of exporting all the required environment variables.

Strengths - Snap packages uses squashfs which is also used in type 2 AppImages which could potentially ease the building process - Final package apps “could” be turned into AppImages

Drawbacks - Vendor lock-in courtesy of Canonical - Developers will need to have deal with yet another dependencies management system - Almost every package would have to be redefined/rebuilt on a old enough system

  1. Flatpak

    Three different concepts are used in Flatpak to deal with dependencies: runtimes, bundled libraries and base apps. Runtimes provides a set of basic dependencies to be used by the applications. Bundled libraries are used to extend the runtimes and the bundling process is quite similar to the one used to make an AppImage (manual bundling). Base apps are like extended and specialized runtimes to be used while packaging by example an Electron application.

    As runtimes are meant to be ‘portable’ and base apps they “could” be used as base for building AppImages. Developers should only install the required runtime to develop their apps. Bundled libraries are not a big improvement compared to the current AppImage production process.


    • More “open” than snaps?
    • Final package apps “could” be turned into AppImages


    • Developers will need to have deal with yet another dependencies management system
    • Almost every package would have to be redefined/rebuilt on a old enough system
    • If a rare (not included in any runtime) dependency is required it doesn’t provide any real improvement over manual dependency management.
  2. Conan

    Conan is a portable package manager, intended for C and C++ developers, but it is able to manage builds from source, dependencies, and pre-compiled binaries for any language. It is focused on resolving development dependencies (which also implies run-time dependencies) so it allows to reconfigure/rebuild a given package and its dependencies with a minimal effort. In combination with Artifactory a self-hosted dependencies repository could be easily created. It already has a solid integration with docker making tasks like cross-compilation really simple.

    Dependencies must be packed before using them. Conan uses python in its configuration files. Developers must create a file where the dependencies are specified. Then use conan install to download them. This will create a development environment equal to the packaging environment which save a lot of work while creating the packages.


    • Development oriented
    • Development environment equal to the packaging environment
    • Simple rebuild and reconfiguration of dependencies
    • AppImages could be created from the development environment without needing an old enough system


    • Developers will need to have deal with yet another dependencies management system
    • Some libraries will required proper packaging


All of the review solutions allows to create a crowd-sourced repository of relocatable and backward compatible binaries. Which means that the dependencies packaging efforts will be shared among all the AppImage creators. But we can discriminate them attending to their strengths and drawbacks being an additional goal to also reduce development and maintenance efforts of the AppImage development team.

GNU/Linux distributions (at least Debian, OpenSuse, Centos, Ubuntu, Fedora, Arch) compatibility is required. Traditional distributions repositories are compatible with only one of the above mentioned. Having one repository for each distributions implies a lot of work. Therefore it’s excluded. Flatpack and Snappy provides implementations for such distributions. Conan runs on python so it’s also compatible.

Completely open-source is mandatory. Most of the Snappy technologies are open but the store in closed source. A new store will have to be developed. Flatpack and Conan + Artifactory are totally open source. Therefore it’s excluded.

Comparing Flatpack and Conan it’s found that both are a ‘new dependencies management system’ to the developer deal with. But this is not a big issue if we consider that almost any modern software development technology has one of those. Both solutions already has packages that could be turned into AppImages or could be used to build AppImages. And also there are many libraries that would require to be repacked. The main difference resides in the focus of each solution. Flatpack is focused only on distributing software. Conan on the other hand is focused on distributing development dependencies (which also include the run-time dependencies) and it also provides a set of tools to make such dependencies relocatable and backward compatible.

Additionally Conan provides simple rebuild and reconfiguration of dependencies to make any small adjustment required by the developer. By example choosing between using a shared library or a static one. And the most important feature of Conan would be making the development environment equal to the packaging environment. This allows to identify compatibility issues early in the development/packaging process and to create backward compatible binaries on modern systems.

Final applications could be packaged with Conan but the result is not quite user-friendly. Therefore AppImage could also be the right complement to Conan. files could be used to produce AppImages which contributes to the goal of having reproducible AppImage builds.

In conclusion Conan and AppImage seems to be done one for each other. Both solutions are a complementary and share similar goals regarding to binaries production. The AppImage project will gain dependency management system and Conan will gain an application packaging solution.



Akademy 2018 Impressions

Akademy is, according to its web page, the annual world summit of KDE, one of the largest Free Software communities in the world. I would add to that is a great opportunity to meet really creative tech people, to learn and to get more involved into the Free Software world. This was my first time attending to it, and probably not the last one. I attended as a plasma extensions developer, as Nitrux developer and also as an AppImage Project contributor.

I wasn’t able to get presentation ready on time ready but I do had the chance to discuss about the above mentioned projects with the people around. So I’ll share the a summary.

Plasma Extensions

Is composed by a set of experimental plasmoids that follow a design goal: bring the most used and related settings together and upfront.

  1. Plasma Widget Quick Controls

This widget is to group together all the controls that a novice user will require and is meant to replace the network, Bluetooth, Audio and Power plasmoids.

Plasma Widget Quick Controls
  1. Extended Volume Mixer Widget

The goal behind this plasmoid is to make really accessible the configuration of multiple audio devices.

Extended Volume Mixer
  1. Notifications sidebar

Provides a fancy and easy to access area for your system notifications.

Notifications side bar


Is a GNU/Linux distribution focused on providing the best user experience possible. It combines an elegant design and a set of enhanced plasma widgets that group together the mos commonly used functionalities. It’s based (at the time writing this post) on ubuntu 18.04 and uses AppImages as the main way of distributing user applications.

In Akademy we, the Nitrux team, had the chance to present our work in the distributions BoF. Which included the NX Software Center which is a Qt-Qml application that makes usage of the plasma qml components to achieve a better blending with Plasma based desktops. Also it’s distributed as an AppImage which makes it a good reference of applications that makes use of the plasma qml components and kde frameworks and want to be distributed in the same way.


As active contributor to the AppImage project I was presenting the AppImage KDE Thumbnailer. Also was discussed how to improve AppImages support in Plasma, therefore were requested the following features:

  • AppImage files thumbnails in the file manager.
  • Applications menu, mime-types and favorite applications integration.
  • Execution and verification of newly downloaded AppImage files.
  • Discovery newly available AppImages in the file system.

It was really great to see that our requests were listened and analysed carefully. We get to the arrangement that once the basic libs for AppImage manipulation were included in the major upstream projects the repositories we could continue working on the topic.


After a whole week of really interesting presentations, workshops and high tech I got the feeling of being part of something really awesome, the creation of a better and free software ecosystem for the world. The people there were really nice and the organization was awesome. In general, Akademy 2018 was a great opportunity to share experiences, results and also to make friends.