1FLATPAK OVERRIDE(1)            flatpak override            FLATPAK OVERRIDE(1)
2
3
4

NAME

6       flatpak-override - Override application requirements
7

SYNOPSIS

9       flatpak override [OPTION...] [APP]
10

DESCRIPTION

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
16       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
21       If the application id is not specified then the overrides affect all
22       applications, but the per-application overrides can override the global
23       overrides.
24
25       Unless overridden with the --user or --installation options, this
26       command changes the default system-wide installation.
27

OPTIONS

29       The following options are understood:
30
31       -h, --help
32           Show help options and exit.
33
34       --user
35           Update a per-user installation.
36
37       --system
38           Update the default system-wide installation.
39
40       --installation=NAME
41           Updates a system-wide installation specified by NAME among those
42           defined in /etc/flatpak/installations.d/. Using
43           --installation=default is equivalent to using --system.
44
45       --share=SUBSYSTEM
46           Share a subsystem with the host session. This overrides the Context
47           section from the application metadata.  SUBSYSTEM must be one of:
48           network, ipc. This option can be used multiple times.
49
50       --unshare=SUBSYSTEM
51           Don't share a subsystem with the host session. This overrides the
52           Context section from the application metadata.  SUBSYSTEM must be
53           one of: network, ipc. This option can be used multiple times.
54
55       --socket=SOCKET
56           Expose a well-known socket to the application. This overrides to
57           the Context section from the application metadata.  SOCKET must be
58           one of: x11, wayland, fallback-x11, pulseaudio, system-bus,
59           session-bus, ssh-auth, pcsc. This option can be used multiple
60           times.
61
62       --nosocket=SOCKET
63           Don't expose a well-known socket to the application. This overrides
64           to the Context section from the application metadata.  SOCKET must
65           be one of: x11, wayland, fallback-x11, pulseaudio, system-bus,
66           session-bus, ssh-auth, pcsc. This option can be used multiple
67           times.
68
69       --device=DEVICE
70           Expose a device to the application. This overrides to the Context
71           section from the application metadata.  DEVICE must be one of: dri,
72           kvm, all. This option can be used multiple times.
73
74       --nodevice=DEVICE
75           Don't expose a device to the application. This overrides to the
76           Context section from the application metadata.  DEVICE must be one
77           of: dri, kvm, all. This option can be used multiple times.
78
79       --allow=FEATURE
80           Allow access to a specific feature. This updates the [Context]
81           group in the metadata.  FEATURE must be one of: devel, multiarch,
82           bluetooth, canbus. This option can be used multiple times.
83
84           See flatpak-build-finish(1) for the meaning of the various
85           features.
86
87       --disallow=FEATURE
88           Disallow access to a specific feature. This updates the [Context]
89           group in the metadata.  FEATURE must be one of: devel, multiarch,
90           bluetooth, canbus. This option can be used multiple times.
91
92       --filesystem=FILESYSTEM
93           Allow the application access to a subset of the filesystem. This
94           overrides to the Context section from the application metadata.
95           FILESYSTEM can be one of: home, host, xdg-desktop, xdg-documents,
96           xdg-download, xdg-music, xdg-pictures, xdg-public-share,
97           xdg-templates, xdg-videos, xdg-run, xdg-config, xdg-cache,
98           xdg-data, an absolute path, or a homedir-relative path like ~/dir
99           or paths relative to the xdg dirs, like xdg-download/subdir. The
100           optional :ro suffix indicates that the location will be read-only.
101           The optional :create suffix indicates that the location will be
102           read-write and created if it doesn't exist. This option can be used
103           multiple times.
104
105       --nofilesystem=FILESYSTEM
106           Remove access to the specified subset of the filesystem from the
107           application. This overrides to the Context section from the
108           application metadata.  FILESYSTEM can be one of: home, host,
109           xdg-desktop, xdg-documents, xdg-download, xdg-music, xdg-pictures,
110           xdg-public-share, xdg-templates, xdg-videos, an absolute path, or a
111           homedir-relative path like ~/dir. This option can be used multiple
112           times.
113
114       --add-policy=SUBSYSTEM.KEY=VALUE
115           Add generic policy option. For example,
116           "--add-policy=subsystem.key=v1 --add-policy=subsystem.key=v2" would
117           map to this metadata:
118
119               [Policy subsystem]
120               key=v1;v2;
121
122
123           This option can be used multiple times.
124
125       --remove-policy=SUBSYSTEM.KEY=VALUE
126           Remove generic policy option. This option can be used multiple
127           times.
128
129       --env=VAR=VALUE
130           Set an environment variable in the application. This overrides to
131           the Context section from the application metadata. This option can
132           be used multiple times.
133
134       --own-name=NAME
135           Allow the application to own the well-known name NAME on the
136           session bus. This overrides to the Context section from the
137           application metadata. This option can be used multiple times.
138
139       --talk-name=NAME
140           Allow the application to talk to the well-known name NAME on the
141           session bus. This overrides to the Context section from the
142           application metadata. This option can be used multiple times.
143
144       --no-talk-name=NAME
145           Don't allow the application to talk to the well-known name NAME on
146           the session bus. This overrides to the Context section from the
147           application metadata. This option can be used multiple times.
148
149       --system-own-name=NAME
150           Allow the application to own the well known name NAME on the system
151           bus. If NAME ends with .*, it allows the application to own all
152           matching names. This overrides to the Context section from the
153           application metadata. This option can be used multiple times.
154
155       --system-talk-name=NAME
156           Allow the application to talk to the well known name NAME on the
157           system bus. If NAME ends with .*, it allows the application to talk
158           to all matching names. This overrides to the Context section from
159           the application metadata. This option can be used multiple times.
160
161       --system-no-talk-name=NAME
162           Don't allow the application to talk to the well known name NAME on
163           the system bus. If NAME ends with .*, it allows the application to
164           talk to all matching names. This overrides to the Context section
165           from the application metadata. This option can be used multiple
166           times.
167
168       --persist=FILENAME
169           If the application doesn't have access to the real homedir, make
170           the (homedir-relative) path FILENAME a bind mount to the
171           corresponding path in the per-application directory, allowing that
172           location to be used for persistent data. This overrides to the
173           Context section from the application metadata. This option can be
174           used multiple times.
175
176       --reset
177           Remove overrides. If an APP is given, remove the overrides for that
178           application, otherwise remove the global overrides.
179
180       --show
181           Shows overrides. If an APP is given, shows the overrides for that
182           application, otherwise shows the global overrides.
183
184       -v, --verbose
185           Print debug information during command processing.
186
187       --ostree-verbose
188           Print OSTree debug information during command processing.
189

EXAMPLES

191       $ flatpak override --nosocket=wayland org.gnome.gedit
192
193       $ flatpak override --filesystem=home org.mozilla.Firefox
194

SEE ALSO

196       flatpak(1), flatpak-run(1)
197
198
199
200flatpak                                                    FLATPAK OVERRIDE(1)
Impressum