Page MenuHomeVyOS Platform

Container configuration upgrade destroys system
Open, HighPublicBUG

Description

When upgrading a vyos system containing container configuration, the configuration will be destroyed, such as the following configuration:

set interfaces ethernet eth0 address dhcp
set interfaces ethernet eth0 ipv6 address autoconf
set system name-service 114.114.114.114
set container name nginx image nginx
set container name nginx allow-host-networks
commit
save
exit

Then, upgrade the vyos:

add system image https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso
reboot

Restart after the first upgrade:

Restart after the second upgrade:

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)

Event Timeline

In the latest rolling release all works fine without any changes

vyos@r1-roll:~$ show version 

Version:          VyOS 1.4-rolling-202107010537
Release Train:    sagitta

vyos@r1-roll:~$ sudo podman  run --net host --rm fedora echo it works
it works
vyos@r1-roll:~$

note: Record the process of upgrading from 1.4-rolling-202107010537 to 1.4-rolling-202107122017

After the first startup, the container fails to start. Restart the operating system and start normally.

Wait for the next test to determine if this problem is resolved!

Unfortunately, it seems that the same problem still happened. Although it seems that the container can be started normally after restart due to priority adjustment and some factors, it is not a normal operation result!