Man page - flatpak-override(1)
Packages contas this manual
- flatpak-update(1)
- flatpak-ps(1)
- flatpak-document-unexport(1)
- flatpak-build-import-bundle(1)
- flatpak-repo(1)
- flatpak-build-init(1)
- flatpak-flatpakref(5)
- flatpak-enter(1)
- flatpak-spawn(1)
- flatpak-build-update-repo(1)
- flatpak-build-export(1)
- flatpak-config(1)
- flatpakrepo(5)
- flatpak-make-current(1)
- flatpak-document-info(1)
- flatpak-permission-set(1)
- flatpak-run(1)
- flatpak-permission-reset(1)
- flatpak-repair(1)
- flatpak-remote-ls(1)
- flatpak-remote-info(1)
- flatpak-remote-delete(1)
- flatpakref(5)
- flatpak-search(1)
- flatpak-kill(1)
- flatpak-document-export(1)
- flatpak-remote-add(1)
- flatpak-build-bundle(1)
- flatpak-uninstall(1)
- flatpak-permission-show(1)
- flatpak-info(1)
- flatpak-remotes(1)
- flatpak-remote(5)
- flatpak-create-usb(1)
- flatpak-build-finish(1)
- flatpak-installation(5)
- flatpak-pin(1)
- flatpak-permissions(1)
- flatpak-build-sign(1)
- flatpak-install(1)
- flatpak-mask(1)
- flatpak-documents(1)
- flatpak-build-commit-from(1)
- flatpak(1)
- flatpak-flatpakrepo(5)
- flatpak-permission-remove(1)
- flatpak-list(1)
- flatpak-remote-modify(1)
- flatpak-override(1)
- flatpak-history(1)
- flatpak-build(1)
- flatpak-metadata(5)
apt-get install flatpak
Manual
| FLATPAK OVERRIDE(1) | flatpak override | FLATPAK OVERRIDE(1) |
NAME
flatpak-override - Override application requirements
SYNOPSIS
flatpak override [OPTION...] [APP]
DESCRIPTION
Overrides the application specified runtime requirements. This can be used to grant a sandboxed application more or less resources than it requested.
By default the application gets access to the resources it requested when it is started. But the user can override it on a particular instance by specifying extra arguments to flatpak run, or every time by using flatpak override.
The application overrides are saved in text files residing in $XDG_DATA_HOME/flatpak/overrides in user mode.
If the application ID APP is not specified then the overrides affect all applications, but the per-application overrides can override the global overrides.
Unless overridden with the --user or --installation options, this command changes the default system-wide installation.
OPTIONS
The following options are understood:
-h, --help
-u, --user
--system
--installation=NAME
--share=SUBSYSTEM
--unshare=SUBSYSTEM
--socket=SOCKET
--nosocket=SOCKET
--device=DEVICE
--nodevice=DEVICE
--allow=FEATURE
See flatpak-build-finish(1) for the meaning of the various features.
--disallow=FEATURE
--filesystem=FILESYSTEM
--nofilesystem=FILESYSTEM
This option does not prevent access to a more narrowly-scoped --filesystem. For example, if an application has the equivalent of --filesystem=xdg-config/MyApp in its manifest or as a system-wide override, and flatpak override --user --nofilesystem=home as a per-user override, then it will be prevented from accessing most of the home directory, but it will still be allowed to access $XDG_CONFIG_HOME/MyApp.
As a special case, --nofilesystem=host:reset will ignore all --filesystem permissions inherited from the app manifest or a lower-precedence layer of overrides, in addition to having the behaviour of --nofilesystem=host.
--add-policy=SUBSYSTEM.KEY=VALUE
[Policy subsystem] key=v1;v2;
This option can be used multiple times.
--remove-policy=SUBSYSTEM.KEY=VALUE
--env=VAR=VALUE
--unset-env=VAR
--env-fd=FD
Each environment variable is in the form VAR=VALUE followed by a zero byte. This is the same format used by env -0 and /proc/*/environ.
--own-name=NAME
--talk-name=NAME
--no-talk-name=NAME
--system-own-name=NAME
--system-talk-name=NAME
--system-no-talk-name=NAME
--persist=FILENAME
--reset
--show
-v, --verbose
--ostree-verbose
EXAMPLES
$ flatpak override --nosocket=wayland org.gnome.gedit
$ flatpak override --filesystem=home org.mozilla.Firefox
SEE ALSO
flatpak(1), flatpak-run(1)
| flatpak |