Building your first Flatpak¶
This tutorial provides a quick introduction to building Flatpaks. In it, you will learn how to create a basic Flatpak application, which can be installed and run.
In order to complete this tutorial, you should have followed the setup guide
on flatpak.org. You also need to have installed
flatpak-builder, which is usually available from the same repository as
flatpak package (e.g. use
dnf). You can also install
it as a flatpak with
flatpak install flathub org.flatpak.Builder.
1. Install a runtime and the matching SDK¶
Flatpak requires every app to specify a runtime that it uses for its basic dependencies. Each runtime has a matching SDK (Software Development Kit), which contains all the things that are in the runtime, plus headers and development tools. This SDK is required to build apps for the runtime.
In this tutorial we will use the Freedesktop 19.08 runtime and SDK. To install these, run:
$ flatpak install flathub org.freedesktop.Platform//19.08 org.freedesktop.Sdk//19.08
2. Create the app¶
The app that is going to be created for this tutorial is a simple script. To create it, copy the following:
#!/bin/sh echo "Hello world, from a sandbox"
Now paste this into an empty file and save it as
3. Add a manifest¶
Each Flatpak is built using a manifest file which provides basic information about the application and instructions for how it is to be built. To add a manifest to the hello world app, add the following to an empty file:
app-id: org.flatpak.Hello runtime: org.freedesktop.Platform runtime-version: '19.08' sdk: org.freedesktop.Sdk command: hello.sh modules: - name: hello buildsystem: simple build-commands: - install -D hello.sh /app/bin/hello.sh sources: - type: file path: hello.sh
Now save the file alongside
hello.sh and call it
In a more complex application, the manifest would list multiple modules. The last one would typically be the application itself, and the earlier ones would be dependencies that are bundled with the app because they are not part of the runtime.
4. Build the application¶
Now that the app has a manifest,
flatpak-builder can be used to build it.
This is done by specifying the manifest file and a target directory:
$ flatpak-builder build-dir org.flatpak.Hello.yml
This command will build each module that is listed in the manifest and install
it to the
/app subdirectory, inside the
5. Test the build¶
To verify that the build was successful, run the following:
$ flatpak-builder --run build-dir org.flatpak.Hello.yml hello.sh
Congratulations, you’ve made an app!
--run results in a sandbox with mostly the same permissions as the
final app, with the exception of filesystem permissions. As such it shouldn’t
be relied upon beyond basic testing.
6. Put the app in a repository¶
Before you can install and run the app, it first needs to be put in a
repository. This is done by passing the
--repo argument to
$ flatpak-builder --repo=repo --force-clean build-dir org.flatpak.Hello.yml
This does the build again, and at the end exports the result to a local
repo. Note that
flatpak-builder keeps a cache of
previous builds in the
.flatpak-builder subdirectory, so doing a second
build like this is very fast.
This second time we passed in
--force-clean, which means that the
build-dir directory was deleted before the new build was
In order for your application to show up in application stores while testing with a local repository, you might have
flatpak build-update-repo repo.
For more information how to publish to application stores see Appdata files.
7. Install the app¶
Now we’re ready to add the repository that was just created and install the app. This is done with two commands:
$ flatpak --user remote-add --no-gpg-verify tutorial-repo repo $ flatpak --user install tutorial-repo org.flatpak.Hello
The first command adds the repository that was created in the previous step. The second command installs the app from the repository.
Both these commands use the
--user argument, which means that the
repository and the app are added per-user rather than system-wide. This is
useful for testing.
Note that the repository was added with
--no-gpg-verify, since a GPG key
wasn’t specified when the app was built. This is fine for testing, but for
official repositories you should sign them with a private GPG key.
8. Run the app¶
All that’s left is to try the app. This can be done with the following command:
$ flatpak run org.flatpak.Hello
This runs the app, so that it prints ‘Hello world, from a sandbox’.