flatpak run flatpak Developer Alexander Larsson alexl@redhat.com flatpak run 1 flatpak-run Run an application flatpak run OPTION APP ARG Description Runs an application in a sandboxed environment. APP must name an installed application. Extra arguments are passed on to the application. flatpak creates a sandboxed environment for the application to run in by mounting the right runtime at /usr and a writable directory at /var, whose content is preserved between application runs. The application itself is mounted at /app. The details of the sandboxed environment are controlled by the application metadata and various options like --share and --socket that are passed to the run command: Access is allowed if it was requested either in the application metadata file or with an option and the user hasn't overridden it. Options The following options are understood: Show help options and exit. Print debug information during command processing. Print version information and exit. The architecture to install for. The command to run instead of the one listed in the application metadata. The branch to use. Use the devel runtime that is specified in the application metadata instead of the regular runtime. Use this runtime instead of the one that is specified in the application metadata. This is a full tuple, like for example org.freedesktop.Sdk/x86_64/1.2, but partial tuples are allowed. Any empty or missing parts are filled in with the corresponding values specified by the app. Use this version of the runtime instead of the one that is specified in the application metadata. This overrides any version specified with the --runtime option. Share a subsystem with the host session. This overrides the Context section from the application metadata. SUBSYSTEM must be one of: network, ipc. This option can be used multiple times. Don't share a subsystem with the host session. This overrides the Context section from the application metadata. SUBSYSTEM must be one of: network, ipc. This option can be used multiple times. Expose a well known socket to the application. This overrides to the Context section from the application metadata. SOCKET must be one of: x11, wayland, pulseaudio, system-bus, session-bus. This option can be used multiple times. Don't expose a well known socket to the application. This overrides to the Context section from the application metadata. SOCKET must be one of: x11, wayland, pulseaudio, system-bus, session-bus. This option can be used multiple times. Expose a device to the application. This overrides to the Context section from the application metadata. DEVICE must be one of: dri. This option can be used multiple times. Don't expose a device to the application. This overrides to the Context section from the application metadata. DEVICE must be one of: dri. This option can be used multiple times. Allow the application access to a subset of the filesystem. This overrides to the Context section from the application metadata. FS can be one of: home, host, xdg-desktop, xdg-documents, xdg-download xdg-music, xdg-pictures, xdg-public-share, xdg-templates, xdg-videos, xdg-run, an absolute path, or a homedir-relative path like ~/dir or paths relative to the xdg dirs, like xdg-download/subdir. This option can be used multiple times. Set an environment variable in the application. This overrides to the Context section from the application metadata. This option can be used multiple times. Allow the application to own the well known name NAME on the session bus. If NAME ends with .*, it allows the application to own all matching names. This overrides to the Context section from the application metadata. This option can be used multiple times. Allow the application to talk to the well known name NAME on the session bus. If NAME ends with .*, it allows the application to talk to all matching names. This overrides to the Context section from the application metadata. This option can be used multiple times. Allow the application to own the well known name NAME on the system bus. If NAME ends with .*, it allows the application to own all matching names. This overrides to the Context section from the application metadata. This option can be used multiple times. Allow the application to talk to the well known name NAME on the system bus. If NAME ends with .*, it allows the application to talk to all matching names. This overrides to the Context section from the application metadata. This option can be used multiple times. If the application doesn't have access to the real homedir, make the (homedir-relative) path FILENAME a bind mount to the corresponding path in the per-application directory, allowing that location to be used for persistent data. This overrides to the Context section from the application metadata. This option can be used multiple times. Log session bus traffic. This can be useful to see what access you need to allow in your D-Bus policy. Log system bus traffic. This can be useful to see what access you need to allow in your D-Bus policy. Examples $ flatpak run org.gnome.GEdit $ flatpak run --devel --command=bash org.gnome.Builder See also flatpak1 flatpak-override1 flatpak-enter1