-
-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incus image export puts wrong creation_date #1371
Comments
Closes lxc#1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
@stgraber I just tested your branch and it does not seem to fix the issue. See:
EDIT: I'm sorry I did not understand that
(actually I also discovered that I just need to extract metadata.yaml from Also in the debug logs I can see:
So /shrug |
Closes lxc#1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes lxc#1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Closes #1371 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Required information
Issue description
When using
incus image export
, themetadata.yaml
in the tarball might have a wrongcreation_date
field. For example today (13 november) the images exported (and imported by simplestreams) have a date of the 6th of november…Steps to reproduce
incus launch imageX container
incus stop container
incus publish container imageY
incus image show imageY
show the correct creation date (right now)incus image export imageY imageY
createsimageY.tar.gz
withmetadata.yaml
… THAT CONTAINS imageX's CREATION DATE!Also, imageY's expiry date is 1 month after imageX's creation, not imageY…
So it looks like the creation_date "leaks" via container launch / publication ?
Information to attach
dmesg
)incus info NAME --show-log
)incus config show NAME --expanded
)incus monitor --pretty
while reproducing the issue)The text was updated successfully, but these errors were encountered: