News for hackers. Stuff that matters.
Re:Introducing Google Container-VM Image by dekhn on Friday September 30, 2016 @10:14PM (#12616269)
I imagine it would be trivial: start an image, then capture the filesystem image, then patch up anything where the image depended on Google Cloud.
Re:Introducing Google Container-VM Image by skj on Friday September 30, 2016 @10:47PM (#12616332)
Just to be clear, the "would be trivial" part was a joke, right?
Re:Introducing Google Container-VM Image by dekhn on Saturday October 01, 2016 @08:27AM (#12617579)
Every time I've cloned a Linux image from one infrastructure provider to another, I've always had to identify 5-10 locations where it was customized for the infrastructure. Typically finding those is a matter of reading log files and knowing how linux works. To me, that's "trivial" because it's something I've been doing for decades. It may not be so for other people.
Re:Introducing Google Container-VM Image by threeseed on Friday September 30, 2016 @11:19PM (#12616392)
Since you can SSH into the running image you can just use rsync to clone the entire disk. Is there something you know that is being missed here ?
Re:Introducing Google Container-VM Image by Natanael_L on Saturday October 01, 2016 @07:28AM (#12617420)
I'm thinking they're expecting it to be heavily reliant on Google infrastructure through a variety of API calls.