mirror of
https://github.com/containers/podman.git
synced 2025-08-06 11:32:07 +08:00
podman machine: disable zincati update service
As explained in #21022, there are all kinds of downsides to a machine updating itself (via zincati) automatically, like interuption of service, lost mounts, etc. disabling zincati will at least allow stop these downsides. we are likely to contemplate if podman will take over the update process externally where interuption of services will not occur etc. Fixes #20122 Signed-off-by: Brent Baude <bbaude@redhat.com>
This commit is contained in:
@ -24,7 +24,30 @@ but can be optionally used on Linux.
|
||||
SSH keys are automatically generated to access the VM, and system connections to the root account
|
||||
and a user account inside the VM are added.
|
||||
|
||||
By default, the VM distribution is [Fedora CoreOS](https://getfedora.org/en/coreos?stream=testing).
|
||||
By default, the VM distribution is [Fedora CoreOS](https://getfedora.org/en/coreos?stream=testing) except for
|
||||
WSL which is based on a custom Fedora image. While Fedora CoreOS upgrades come out every 14 days, the automatic
|
||||
update mechanism Zincata is disabled by Podman machine.
|
||||
|
||||
To check if there is an upgrade available for your machine os, you can run the following command:
|
||||
|
||||
```
|
||||
$ podman machine ssh 'sudo rpm-ostree upgrade --check'
|
||||
|
||||
```
|
||||
If an update is available, you can rerun the above command and remove the `--check` and your operating system will
|
||||
be updated. After updating, you must stop and start your machine with `podman machine stop && podman machine start` for
|
||||
it to take effect.
|
||||
|
||||
Note: Updating as described above can result in version mismatches between Podman on the host and Podman in the
|
||||
machine. Executing `podman info` should reveal versions of both. A configuration where the Podman host and machine
|
||||
mismatch are unsupported.
|
||||
|
||||
For more information on updates and advanced configuration,
|
||||
see the Fedora CoreOS documentation about [auto-updates](https://docs.fedoraproject.org/en-US/fedora-coreos/auto-updates/) and [update strategies](https://coreos.github.io/zincati/usage/updates-strategy/).
|
||||
|
||||
|
||||
|
||||
|
||||
Fedora CoreOS upgrades come out every 14 days and are detected and installed automatically. The VM is rebooted during the upgrade.
|
||||
For more information on updates and advanced configuration,
|
||||
see the Fedora CoreOS documentation about [auto-updates](https://docs.fedoraproject.org/en-US/fedora-coreos/auto-updates/) and [update strategies](https://coreos.github.io/zincati/usage/updates-strategy/).
|
||||
@ -78,6 +101,9 @@ Set the timezone for the machine and containers. Valid values are `local` or
|
||||
a `timezone` such as `America/Chicago`. A value of `local`, which is the default,
|
||||
means to use the timezone of the machine host.
|
||||
|
||||
The timezone setting is not used with WSL. WSL automatically sets the timezone to the same
|
||||
as the host Windows operating system.
|
||||
|
||||
@@option user-mode-networking
|
||||
|
||||
#### **--username**
|
||||
|
Reference in New Issue
Block a user