Translations by Noa Himesaka

The advise-snap command searches for and suggests the installation of snaps. If --command is given, it suggests snaps that provide the given command. Otherwise it suggests snaps with the given name.

The aliases command lists all aliases available in the system and their status. $ snap aliases <snap> Lists only the aliases defined by the specified snap. An alias noted as undefined means it was explicitly enabled or disabled but is not defined in the current revision of the snap, possibly temporarily (e.g. because of a revert). This can cleared with 'snap alias --reset'.

The confinement command will print the confinement mode (strict, partial or none) the system operates in.

The download command downloads the given snap and its supporting assertions to the current directory with .snap and .assert file extensions, respectively.

The export-key command exports a public key assertion body that may be imported by other systems.

The file-access command returns information about a snap's file system access. This command is used by the xdg-document-portal service to identify files that do not need to be proxied to provide access within confinement. File paths are interpreted as host file system paths. The tool may return false negatives (e.g. report that a file path is unreadable, despite being readable under a different path). It also does not check if file system permissions would render a file unreadable.

The find command queries the store for available packages. With the --private flag, which requires the user to be logged-in to the store (see 'snap help login'), it instead searches for private snaps that the user has developer access to, either directly or through the store's collaboration feature. A green check mark (given color and unicode support) after a publisher name indicates that the publisher has been verified.

The info command shows detailed information about snaps. The snaps can be specified by name or by path; names are looked for both in the store and in the installed snaps; paths can refer to a .snap file, or to a directory that contains an unpacked snap suitable for 'snap try' (an example of this would be the 'prime' directory snapcraft produces).

The interfaces command lists interfaces available in the system. By default all slots and plugs, used and offered by all snaps, are displayed. $ snap interfaces <snap>:<slot or plug> Lists only the specified slot or plug. $ snap interfaces <snap> Lists the slots offered and plugs used by the specified snap. $ snap interfaces -i=<interface> [<snap>] Filters the complete output so only plugs and/or slots matching the provided details are listed. NOTE this command is deprecated and has been replaced with the 'connections' command.

The model command returns the active model assertion information for this device. By default, only the essential model identification information is included in the output, but this can be expanded to include all of an assertion's non-meta headers. The verbose output is presented in a structured, yaml-like format. Similarly, the active serial assertion can be used for the output instead of the model assertion.

The publisher of snap %q has indicated that they do not consider this revision to be of production quality and that it is only meant for development or testing at this point. As a consequence this snap will not refresh automatically and may perform arbitrary system changes outside of the security sandbox snaps are generally confined to, which may put your system at risk. If you understand and want to proceed repeat the command including --devmode; if instead you want to install the snap forcing it into strict confinement repeat the command including --jailmode.

The recovery command lists the available recovery systems. With --show-keys it displays recovery keys that can be used to unlock the encrypted partitions if the device-specific automatic unlocking does not work.

The remodel command changes the model assertion of the device, either to a new revision or a full new model. In the process it applies any implied changes to the device: new required snaps, new kernel or gadget etc.

The remove command removes the named snap instance from the system. By default all the snap revisions are removed, including their data and the common data directory. When a --revision option is passed only the specified revision is removed. Unless automatic snapshots are disabled, a snapshot of all data for the snap is saved upon removal, which is then available for future restoration with snap restore. The --purge option disables automatically creating snapshots.

The repair command shows the details about one or multiple repairs.

The repairs command lists all processed repairs for this device.

The restart command restarts the given services of the snap. If executed from the "configure" hook, the services will be restarted after the hook finishes.

The restart command restarts the given services. If the --reload option is given, for each service whose app has a reload command, a reload is performed instead of a restart.

The restore command replaces the current user, system and configuration data of included snaps, with the corresponding data from the specified snapshot. By default, this command restores all the data in a snapshot. Alternatively, you can specify the data of which snaps to restore, or for which users, or a combination of these. If a snap is included in a restore operation, excluding its system and configuration data from the restore is not currently possible. This restriction may be lifted in the future.

The revert command reverts the given snap to its state before the latest refresh. This will reactivate the previous snap revision, and will use the original data that was associated with that revision, discarding any data changes that were done by the latest revision. As an exception, data which the snap explicitly chooses to share across revisions is not touched by the revert process.

The routine command contains a selection of additional sub-commands. Routine commands are not intended to be directly invoked by the user. Instead, they are intended to be called by other programs and produce machine readable output.

The run command executes the given snap command with the right confinement and environment.

The sandbox command prints tags describing features of individual sandbox components used by snapd on a given system.

The saved command displays a list of snapshots that have been created previously with the 'save' command.

The services command lists information about the services specified, or about the services in all currently installed snaps.

The services command lists information about the services specified.

%q left the cohort