1FLATPAK INSTALL(1) flatpak install FLATPAK INSTALL(1)
2
6 flatpak-install - Install an application or runtime
7
9 flatpak install [OPTION...] [REMOTE] REF...
10 flatpak install [OPTION...] [--from|--bundle] LOCATION
12
14 Installs an application or runtime. The primary way to install is to
15 specify a REMOTE name as the source and one ore more REFs to specify
16 the application or runtime to install. If REMOTE is omitted, the
17 configured remotes are searched for the first REF and the user is asked
18 to confirm the resulting choice.
19 Each REF argument is a full or partial identifier in the flatpak ref
21 format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
22 except ID are optional and can be left out, including the slashes, so
23 most of the time you need only specify ID. Any part left out will be
24 matched against what is in the remote, and if there are multiple
25 matches you will be prompted to choose one of them. You will also be
26 prompted with choices if REF doesn't match anything in the remote
27 exactly but is similar to one or more refs in the remote (e.g.
28 "devhelp" is similar to "org.gnome.Devhelp").
29 By default this looks for both apps and runtimes with the given REF in
31 the specified REMOTE, but you can limit this by using the --app or
32 --runtime option, or by supplying the initial element in the REF.
33 If REMOTE is a uri or a path (absolute or relative starting with ./) to
35 a local repository, then that repository will be used as the source,
36 and a temporary remote will be created for the lifetime of the REF.
37 If the specified REMOTE has a collection ID configured on it, flatpak
39 will search mounted filesystems such as USB drives as well as Avahi
40 services advertised on the local network for the needed refs, in order
41 to support offline updates. See ostree-find-remotes(1) for more
42 information.
43 The alternative form of the command (with --from or --bundle) allows to
45 install directly from a source such as a .flatpak single-file bundle or
46 a .flatpakref application description. The options are optional if the
47 first argument has the expected filename extension.
48 Note that flatpak allows to have multiple branches of an application
50 and runtimes installed and used at the same time. However, only one
51 version of an application can be current, meaning its exported files
52 (for instance desktop files and icons) are visible to the host. The
53 last installed version is made current by default, but this can
54 manually changed with flatpak make-current.
55 Unless overridden with the --user or the --installation option, this
57 command installs the application or runtime in the default system-wide
58 installation.
59
61 The following options are understood:
62 -h, --help
64 Show help options and exit.
65 --bundle
67 Treat LOCATION as a single-bundle file. This is assumed if the
68 argument ends with .flatpak.
69 --from
71 Treat LOCATION as an application description file. This is assumed
72 if the argument ends with .flatpakref.
73 --reinstall
75 Uninstall first if already installed.
76 --user
78 Install the application or runtime in a per-user installation.
79 --system
81 Install the application or runtime in the default system-wide
82 installation.
83 --installation=NAME
85 Install the application or runtime in a system-wide installation
86 specified by NAME among those defined in
87 /etc/flatpak/installations.d/. Using --installation=default is
88 equivalent to using --system.
89 --arch=ARCH
91 The default architecture to install for, if not given explicitly in
92 the REF. See flatpak --supported-arches for architectures supported
93 by the host.
94 --subpath=PATH
96 Install only a subpath of REF. This is mainly used to install a
97 subset of locales. This can be added multiple times to install
98 multiple subpaths.
99 --gpg-file=FILE
101 Check bundle signatures with GPG key from FILE (- for stdin).
102 --no-deploy
104 Download the latest version, but don't deploy it.
105 --no-pull
107 Don't download the latest version, deploy whatever is locally
108 available.
109 --no-related
111 Don't download related extensions, such as the locale data.
112 --no-deps
114 Don't verify runtime dependencies when installing.
115 --or-update
117 Normally install just ignores things that are already installed
118 (printing a warning), but if --or-update is specified it silently
119 turns it into an update operation instead.
120 --app
122 Assume that all REFs are apps if not explicitly specified.
123 --runtime
125 Assume that all REFs are runtimes if not explicitly specified.
126 --sideload-repo=PATH
128 Adds an extra local ostree repo as source for installation. This is
129 equivalent to using the sideload-repos directories (see
130 flatpak(1)), but can be done on a per-command basis. Any path added
131 here is used in addition to ones in those directories.
132 -y, --assumeyes
134 Automatically answer yes to all questions (or pick the most
135 prioritized answer). This is useful for automation.
136 --noninteractive
138 Produce minimal output and avoid most questions. This is suitable
139 for use in non-interactive situations, e.g. in a build script.
140 -v, --verbose
142 Print debug information during command processing.
143 --ostree-verbose
145 Print OSTree debug information during command processing.
146
148 $ flatpak install gedit
149 $ flatpak install flathub org.gnome.gedit
151 $ flatpak --installation=default install flathub org.gnome.gedit
153 $ flatpak --user install flathub org.gnome.gedit//3.30
155 $ flatpak --user install
157 https://flathub.org/repo/appstream/org.gnome.gedit.flatpakref
158 $ flatpak --system install org.gnome.gedit.flatpakref
160
162 flatpak(1), flatpak-update(1), flatpak-list(1), flatpak-build-
163 bundle(1), flatpak-flatpakref(1), flatpak-make-current(1), ostree-find-
164 remotes(1)
165flatpak FLATPAK INSTALL(1)