Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
lxc inserts /var/lib/cloud/seed/nocloud-net on every start #1747
Comments
|
This is configurable in the image tarball and could be changed to only apply on initial container creation. However should we do so, there would be no way for someone to correct invalid container metadata short of destroy and recreating the container whereas today they can simply wipe /var/lib/cloud/seed clean, reboot and have cloud-init run again. Is there a specific problem with always having the file generated at startup time? |
|
I think its just less expected. I somewhat expect that lxc will do something to configure my system when i first start it, but then i kind of expect that a stop and start its gone. I came across this when working on cloud-init networking to take injected network yaml. and then i'd find that lxc overwrote the files i hand set up. |
|
Okay, I have another change to get into that metadata so I'll bundle that change together when sending the request to the CPC team. |
stgraber
added this to the lxd-2.0.0.rc4 milestone
Mar 11, 2016
stgraber
added
Bug
Easy
labels
Mar 11, 2016
stgraber
self-assigned this
Mar 11, 2016
|
My change has been merged, so this will progressively get fixed as new images roll. |
smoser commentedMar 11, 2016
lxc is inserting the template (seed) files for cloud-init every time. It seems like maybe template files should not be inserted on every start.