1FLATPAK CREATE-USB(1) flatpak create-usb FLATPAK CREATE-USB(1)
2
6 flatpak-create-usb - Copy apps and/or runtimes onto removable media.
7
9 flatpak create-usb [OPTION...] MOUNT-PATH REF...
10
12 Copies the specified apps and/or runtimes REFs onto the removable media
13 mounted at MOUNT-PATH, along with all the dependencies and metadata
14 needed for installing them. This is one way of transferring flatpaks
15 between computers that doesn't require an Internet connection. After
16 using this command, the USB drive can be connected to another computer
17 which already has the relevant remote(s) configured, and Flatpak will
18 install or update from the drive offline (see below). If online, the
19 drive will be used as a cache, meaning some objects will be pulled from
20 it and others from the Internet. For this process to work a collection
21 ID must be configured on the relevant remotes on both the source and
22 destination computers, and on the remote server.
23 On the destination computer one can install from the USB (or any
25 mounted filesystem) using the --sideload-repo option with flatpak
26 install. It's also possible to configure sideload paths using symlinks;
27 see flatpak(1). Flatpak also includes systemd units to automatically
28 sideload from hot-plugged USB drives, but these may or may not be
29 enabled depending on your Linux distribution.
30 Each REF argument is a full or partial identifier in the flatpak ref
32 format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
33 except ID are optional and can be left out, including the slashes, so
34 most of the time you need only specify ID. Any part left out will be
35 matched against what is installed, and if there are multiple matches an
36 error message will list the alternatives.
37 By default this looks for both installed apps and runtimes with the
39 given REF, but you can limit this by using the --app or --runtime
40 option.
41 All REFs must be in the same installation (user, system, or other).
43 Otherwise it's ambiguous which repository metadata refs to put on the
44 USB drive.
45 By default flatpak create-usb uses .ostree/repo as the destination
47 directory under MOUNT-PATH but if you specify another location using
48 --destination-repo a symbolic link will be created for you in
49 .ostree/repos.d. This ensures that either way the repository will be
50 found by flatpak (and other consumers of libostree) for install/update
51 operations.
52 Unless overridden with the --system, --user, or --installation options,
54 this command searches both the system-wide installation and the
55 per-user one for REF and errors out if it exists in more than one.
56
58 The following options are understood:
59 -h, --help
61 Show help options and exit.
62 -u, --user
64 Copy refs from the per-user installation.
65 --system
67 Copy refs from the default system-wide installation.
68 --installation=NAME
70 Copy refs from a system-wide installation specified by NAME among
71 those defined in /etc/flatpak/installations.d/. Using
72 --installation=default is equivalent to using --system.
73 --app
75 Assume that all REFs are apps if not explicitly specified.
76 --runtime
78 Assume that all REFs are runtimes if not explicitly specified.
79 --destination-repo=DEST
81 Create the repository in DEST under MOUNT-PATH, rather than the
82 default location.
83 --allow-partial
85 Don't print a warning when exporting partially installed commits,
86 for example locale extensions without all languages. These can
87 cause problems when installing them, for example if the language
88 config is different on the installing side.
89 -v, --verbose
91 Print debug information during command processing.
92 --ostree-verbose
94 Print OSTree debug information during command processing.
95
97 $ flatpak create-usb
98 /run/media/mwleeds/1a9b4cb2-a7ef-4d9b-91a5-6eaf8fdd2bf6/
99 com.endlessm.wiki_art.en
100
102 flatpak(1), flatpak remote-modify(1), flatpak-install(1), flatpak-
103 list(1), ostree-create-usb(1)
104flatpak FLATPAK CREATE-USB(1)