Hello,
I noticed that if I have an Ubuntu container, and later do a vzrestore of a CentOS container, the OSTEMPLATE variable is not changed in the container config. The side effect of that is that when I start the new container, I get:
Of course, /etc/network/interfaces is where network settings are stored in Ubuntu. vzctl is attempting to check the interfaces file, but being on CentOS, it doesn't exist.
If I change:
to:
everything then works perfectly.
Is it possible to get the variable in the config file updated when we pass the -ostemplate parameter? I think that this would be the ideal behavior.
Thanks!
I noticed that if I have an Ubuntu container, and later do a vzrestore of a CentOS container, the OSTEMPLATE variable is not changed in the container config. The side effect of that is that when I start the new container, I get:
Code:
root@mc02:~# vzctl start 102
Starting container ...
Container is mounted
Adding IP address(es): 10.0.0.100
/bin/bash: line 504: /etc/network/interfaces: No such file or directory
grep: /etc/network/interfaces: No such file or directory
/bin/bash: line 517: /etc/network/interfaces: No such file or directory
/bin/bash: line 540: /etc/network/interfaces: No such file or directory
/bin/bash: line 547: /etc/network/interfaces: No such file or directory
cp: cannot stat `/etc/network/interfaces': No such file or directory
/bin/bash: line 571: /etc/network/interfaces.bak: No such file or directory
mv: cannot stat `/etc/network/interfaces.bak': No such file or directory
Setting CPU units: 1000
Setting CPUs: 1
Container start in progress...If I change:
Code:
OSTEMPLATE="ubuntu-12.04-standard_12.04-1_i386.tar.gz"Code:
OSTEMPLATE="centos-6-standard_6.3-1_i386.tar.gz"Is it possible to get the variable in the config file updated when we pass the -ostemplate parameter? I think that this would be the ideal behavior.
Thanks!