blob: 8bf5b0dc6d354ca57095f9e575f91bf7aa7a28d3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
:lastproofread: 2021-07-26
.. _image-mgmt:
################
Image Management
################
The VyOS image-based installation is implemented by creating a directory for
each image on the storage device selected during the install process.
The directory structure of the boot device:
.. code-block:: none
/
/boot
/boot/grub
/boot/1.2.0-rolling+201810021347
The image directory contains the system kernel, a compressed image of the root
filesystem for the OS, and a directory for persistent storage, such as
configuration. On boot, the system will extract the OS image into memory and
mount the appropriate live-rw sub-directories to provide persistent storage
system configuration.
This process allows for a system to always boot to a known working state, as
the OS image is fixed and non-persistent. It also allows for multiple releases
of VyOS to be installed on the same storage device. The image can be selected
manually at boot if needed, but the system will otherwise boot the image
configured to be the default.
.. opcmd:: show system image
List all available system images which can be booted on the current system.
.. code-block:: none
vyos@vyos:~$ show system image
The system currently has the following image(s) installed:
1: 1.2.0-rolling+201810021347 (default boot)
2: 1.2.0-rolling+201810021217
3: 1.2.0-rolling+201809252218
.. opcmd:: delete system image [image-name]
Delete no longer needed images from the system. You can specify an optional
image name to delete, the image name can be retrieved via a list of available
images using the command :opcmd:`show system image`.
.. code-block:: none
vyos@vyos:~$ delete system image
The following image(s) can be deleted:
1: 1.3-rolling-201912181733 (default boot) (running image)
2: 1.3-rolling-201912180242
3: 1.2.2
4: 1.2.1
Select the image to delete: 2
Are you sure you want to delete the
"1.3-rolling-201912180242" image? (Yes/No) [No]: y
Deleting the "1.3-rolling-201912180242" image...
Done
.. opcmd:: show version
Show current system image version.
.. code-block:: none
vyos@vyos:~$ show version
Version: VyOS 1.3-rolling-201912181733
Built by: autobuild@vyos.net
Built on: Wed 18 Dec 2019 17:33 UTC
Build UUID: bccde2c3-261c-49cc-b421-9b257204e06c
Build Commit ID: f7ce0d8a692f2d
Architecture: x86_64
Boot via: installed image
System type: bare metal
Hardware vendor: VMware, Inc.
Hardware model: VMware Virtual Platform
Hardware S/N: VMware-42 1d 83 b9 fe c1 bd b2-7d 3d 49 db 94 18 f5 c9
Hardware UUID: b9831d42-c1fe-b2bd-7d3d-49db9418f5c9
Copyright: VyOS maintainers and contributors
System rollback
===============
If you need to rollback to a previous image, you can easily do so. First
check the available images through the :opcmd:`show system image`
command and then select your image with the following command:
.. opcmd:: set system image default-boot [image-name]
Select the default boot image which will be started on the next boot
of the system.
Then reboot the system.
.. note:: VyOS automatically associates the configuration to the image,
so you don't need to worry about that. Each image has a unique copy
of its configuration.
If you have access to the console, there is an another way to select
your booting image: reboot and use the GRUB menu at startup.
|
