72ee6598a6
* containers: Pull newer versions of containers Allows topgrade to update a users containers. It will automatically skip containers which come from the `localhost` repo as these are self-built. Respects the version number the containers were initially checked out with in order not to introduce semver-breaking changes. Works with podman and docker. * topgrade: Add 'containers' step * containers: Ignore some errors for docker This patch is needed to achieve compatibility between docker and podman. In particular, docker doesn't store/tell the user from which repository (i.e. `hub.docker.com`, or `registry.fedoraproject.org`) a container originates. This has the side-effect, that self-built containers cannot be distinguished from publicly available containers. Therefore this patch introduces an exception to the error handling when pulling, by scanning the output of the `docker pull` command. If it finds the `registry does not exist` substring in the output, it will skip the container but **NOT** consider the whole update step failed. * containers: Skip '<none>' containers that result from either intermediate products of a container build or when images are dangling. * steps: containers: simplify error handling And don't return errors from within the "unknown container registry" handling, since that would immediately terminate the whole update which isn't intended. |
||
|---|---|---|
| .github | ||
| doc | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| config.example.toml | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
| topgrade.8 | ||
Keeping your system up to date usually involves invoking multiple package managers. This results in big, non-portable shell one-liners saved in your shell. To remedy this, topgrade detects which tools you use and runs the appropriate commands to update them.
Installation
Other systems users can either use cargo install or use the compiled binaries from the release page.
The compiled binaries contain a self-upgrading feature.
Topgrade requires Rust 1.51 or above.
Usage
Just run topgrade.
See the wiki for the list of things Topgrade supports.
Customization
See config.example.toml for an example configuration file.
Configuration path
The configuration should be placed in the following paths depending by the operating system:
- Windows -
%APPDATA%/topgrade.toml - macOS and other Unix systems -
${XDG_CONFIG_HOME:-~/.config}/topgrade.toml
Remote execution
You can specify a key called remote_topgrades in the configuration file.
This key should contain a list of hostnames that have topgrade installed on them.
Topgrade will use ssh to run topgrade on remote hosts before acting locally.
To limit the execution only to specific hosts use the --remote-host-limit parameter.