1FLATPAK OVERRIDE(1) flatpak override FLATPAK OVERRIDE(1)
2
6 flatpak-override - Override application requirements
7
9 flatpak override [OPTION...] [APP]
10
12 Overrides the application specified runtime requirements. This can be
13 used to grant a sandboxed application more or less resources than it
14 requested.
15 By default the application gets access to the resources it requested
17 when it is started. But the user can override it on a particular
18 instance by specifying extra arguments to flatpak run, or every time by
19 using flatpak override.
20 The application overrides are saved in text files residing in
22 $XDG_DATA_HOME/flatpak/overrides in user mode.
23 If the application ID APP is not specified then the overrides affect
25 all applications, but the per-application overrides can override the
26 global overrides.
27 Unless overridden with the --user or --installation options, this
29 command changes the default system-wide installation.
30
32 The following options are understood:
33 -h, --help
35 Show help options and exit.
36 -u, --user
38 Update a per-user installation.
39 --system
41 Update the default system-wide installation.
42 --installation=NAME
44 Updates a system-wide installation specified by NAME among those
45 defined in /etc/flatpak/installations.d/. Using
46 --installation=default is equivalent to using --system.
47 --share=SUBSYSTEM
49 Share a subsystem with the host session. This overrides the Context
50 section from the application metadata. SUBSYSTEM must be one of:
51 network, ipc. This option can be used multiple times.
52 --unshare=SUBSYSTEM
54 Don't share a subsystem with the host session. This overrides the
55 Context section from the application metadata. SUBSYSTEM must be
56 one of: network, ipc. This option can be used multiple times.
57 --socket=SOCKET
59 Expose a well-known socket to the application. This overrides to
60 the Context section from the application metadata. SOCKET must be
61 one of: x11, wayland, fallback-x11, pulseaudio, system-bus,
62 session-bus, ssh-auth, pcsc, cups, gpg-agent. This option can be
63 used multiple times.
64 --nosocket=SOCKET
66 Don't expose a well-known socket to the application. This overrides
67 to the Context section from the application metadata. SOCKET must
68 be one of: x11, wayland, fallback-x11, pulseaudio, system-bus,
69 session-bus, ssh-auth, pcsc, cups, gpg-agent. This option can be
70 used multiple times.
71 --device=DEVICE
73 Expose a device to the application. This overrides to the Context
74 section from the application metadata. DEVICE must be one of: dri,
75 kvm, shm, all. This option can be used multiple times.
76 --nodevice=DEVICE
78 Don't expose a device to the application. This overrides to the
79 Context section from the application metadata. DEVICE must be one
80 of: dri, kvm, shm, all. This option can be used multiple times.
81 --allow=FEATURE
83 Allow access to a specific feature. This updates the [Context]
84 group in the metadata. FEATURE must be one of: devel, multiarch,
85 bluetooth, canbus, per-app-dev-shm. This option can be used
86 multiple times.
87 See flatpak-build-finish(1) for the meaning of the various
89 features.
90 --disallow=FEATURE
92 Disallow access to a specific feature. This updates the [Context]
93 group in the metadata. FEATURE must be one of: devel, multiarch,
94 bluetooth, canbus, per-app-dev-shm. This option can be used
95 multiple times.
96 --filesystem=FILESYSTEM
98 Allow the application access to a subset of the filesystem. This
99 overrides to the Context section from the application metadata.
100 FILESYSTEM can be one of: home, host, host-os, host-etc,
101 xdg-desktop, xdg-documents, xdg-download, xdg-music, xdg-pictures,
102 xdg-public-share, xdg-templates, xdg-videos, xdg-run, xdg-config,
103 xdg-cache, xdg-data, an absolute path, or a homedir-relative path
104 like ~/dir or paths relative to the xdg dirs, like
105 xdg-download/subdir. The optional :ro suffix indicates that the
106 location will be read-only. The optional :create suffix indicates
107 that the location will be read-write and created if it doesn't
108 exist. This option can be used multiple times. See the "[Context]
109 filesystems" list in flatpak-metadata(5) for details of the
110 meanings of these filesystems.
111 --nofilesystem=FILESYSTEM
113 Undo the effect of a previous --filesystem=FILESYSTEM in the app's
114 manifest or a lower-precedence layer of overrides, and/or remove a
115 previous --filesystem=FILESYSTEM from this layer of overrides. This
116 overrides the Context section of the application metadata.
117 FILESYSTEM can take the same values as for --filesystem, but the
118 :ro and :create suffixes are not used here. This option can be used
119 multiple times.
120 This option does not prevent access to a more narrowly-scoped
122 --filesystem. For example, if an application has the equivalent of
123 --filesystem=xdg-config/MyApp in its manifest or as a system-wide
124 override, and flatpak override --user --nofilesystem=home as a
125 per-user override, then it will be prevented from accessing most of
126 the home directory, but it will still be allowed to access
127 $XDG_CONFIG_HOME/MyApp.
128 As a special case, --nofilesystem=host:reset will ignore all
130 --filesystem permissions inherited from the app manifest or a
131 lower-precedence layer of overrides, in addition to having the
132 behaviour of --nofilesystem=host.
133 --add-policy=SUBSYSTEM.KEY=VALUE
135 Add generic policy option. For example,
136 "--add-policy=subsystem.key=v1 --add-policy=subsystem.key=v2" would
137 map to this metadata:
138 [Policy subsystem]
140 key=v1;v2;
141 This option can be used multiple times.
144 --remove-policy=SUBSYSTEM.KEY=VALUE
146 Remove generic policy option. This option can be used multiple
147 times.
148 --env=VAR=VALUE
150 Set an environment variable in the application. This overrides to
151 the Context section from the application metadata. This option can
152 be used multiple times.
153 --unset-env=VAR
155 Unset an environment variable in the application. This overrides
156 the unset-environment entry in the [Context] group of the metadata,
157 and the [Environment] group. This option can be used multiple
158 times.
159 --env-fd=FD
161 Read environment variables from the file descriptor FD, and set
162 them as if via --env. This can be used to avoid environment
163 variables and their values becoming visible to other users.
164 Each environment variable is in the form VAR=VALUE followed by a
166 zero byte. This is the same format used by env -0 and
167 /proc/*/environ.
168 --own-name=NAME
170 Allow the application to own the well-known name NAME on the
171 session bus. This overrides to the Context section from the
172 application metadata. This option can be used multiple times.
173 --talk-name=NAME
175 Allow the application to talk to the well-known name NAME on the
176 session bus. This overrides to the Context section from the
177 application metadata. This option can be used multiple times.
178 --no-talk-name=NAME
180 Don't allow the application to talk to the well-known name NAME on
181 the session bus. This overrides to the Context section from the
182 application metadata. This option can be used multiple times.
183 --system-own-name=NAME
185 Allow the application to own the well known name NAME on the system
186 bus. If NAME ends with .*, it allows the application to own all
187 matching names. This overrides to the Context section from the
188 application metadata. This option can be used multiple times.
189 --system-talk-name=NAME
191 Allow the application to talk to the well known name NAME on the
192 system bus. If NAME ends with .*, it allows the application to talk
193 to all matching names. This overrides to the Context section from
194 the application metadata. This option can be used multiple times.
195 --system-no-talk-name=NAME
197 Don't allow the application to talk to the well known name NAME on
198 the system bus. If NAME ends with .*, it allows the application to
199 talk to all matching names. This overrides to the Context section
200 from the application metadata. This option can be used multiple
201 times.
202 --persist=FILENAME
204 If the application doesn't have access to the real homedir, make
205 the (homedir-relative) path FILENAME a bind mount to the
206 corresponding path in the per-application directory, allowing that
207 location to be used for persistent data. This overrides to the
208 Context section from the application metadata. This option can be
209 used multiple times.
210 --reset
212 Remove overrides. If an APP is given, remove the overrides for that
213 application, otherwise remove the global overrides.
214 --show
216 Shows overrides. If an APP is given, shows the overrides for that
217 application, otherwise shows the global overrides.
218 -v, --verbose
220 Print debug information during command processing.
221 --ostree-verbose
223 Print OSTree debug information during command processing.
224
226 $ flatpak override --nosocket=wayland org.gnome.gedit
227 $ flatpak override --filesystem=home org.mozilla.Firefox
229
231 flatpak(1), flatpak-run(1)
232flatpak FLATPAK OVERRIDE(1)