We made a temporary modification to the local file:
stx-openstack-1.0-78-centos-stable-latest\charts\libvirt-0.1.0\libvirt\templates\daemonset-libvirt.yaml.
The modification method is as follows: lifecycle: postStart:
exec: command:
- bash
- -c
- |- rm -f /etc/localtime ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
After modification, re-upload stx-openstack-1.0-78-centos-stable-latest.tgz in STX system and apply.
The time displayed in the windows VM is consistent with the host time zone, and the correct time display is still maintained after restarting.
The reasonable method we currently analyze is:
...
containers:
- name: libvirt lifecycle: postStart:
exec: command:
- bash
- -c
- |- rm -f /etc/localtime volumeMounts:
- mountPath: /etc/localtime
name: localtime readOnly: true
...
volumes:
- name: localtime
hostPath:
path: /etc/localtime
we don'n know if the community can provide a more efficient modification method.
Thank you so much.
We made a temporary modification to the local file: 1.0-78- centos- stable- latest\ charts\ libvirt- 0.1.0\libvirt\ templates\ daemonset- libvirt. yaml.
lifecycle:
postStart:
command:
rm -f /etc/localtime
ln -s /usr/share/ zoneinfo/ Asia/Shanghai /etc/localtime 1.0-78- centos- stable- latest. tgz in STX system and apply.
stx-openstack-
The modification method is as follows:
exec:
- bash
- -c
- |-
After modification, re-upload stx-openstack-
The time displayed in the windows VM is consistent with the host time zone, and the correct time display is still maintained after restarting.
The reasonable method we currently analyze is:
lifecycle:
postStart:
command:
rm -f /etc/localtime
volumeMounts :
readOnly: true
...
containers:
- name: libvirt
exec:
- bash
- -c
- |-
- mountPath: /etc/localtime
name: localtime
...
volumes:
- name: localtime
hostPath:
path: /etc/localtime
we don'n know if the community can provide a more efficient modification method.
Thank you so much.