Sun, Sep 5
Feb 17 2020
Dec 2 2018
Nov 27 2018
Nov 20 2018
Nov 13 2018
Nov 6 2018
Oct 29 2018
Oct 24 2018
Oct 19 2018
Oct 17 2018
Any further action on this?
I can't find any public images and this thread is a bit lacking in information.
Oct 13 2018
Sep 2 2018
May 27 2018
May 25 2018
May 24 2018
May 11 2018
oh. since this was still open and seemed to have died I assumed there wasn't any image for GCE yet. Well that's good - is the image public?
It's still missing cloud-init part and google agent (not recall how called that piece of software)
otherwise it's working on gcp and azure
I've started to try to convert the official ansible playbooks used to build the AMI for use on building a GCE image. Hopefully I'll have something working this weekend and can post here for some wider testing. I'm starting from the method here: https://github.com/vyos/build-ami Not the method mentioned earlier in this task using Packer.
Mar 6 2018
Nov 11 2017
Jul 24 2017
Mar 7 2017
I don't know enough to be able to do this in GCE without some help, not sure where to start. I was using the AWS packer image as an example but got stuck. If I have something to go off of, I can use that and work through it and/or ask questions as needed.
Feb 18 2017
Feb 17 2017
Is this en-devour dead? I really want to help but I wonder I'd be much use. If there's any dumb testing or boring tasks let me know.
Feb 6 2017
with ubuntu 14.04 I still get the error above.
mount: wrong fs type, bad option, bad superblock on overlayfs,
Feb 4 2017
@syncer yes please split it off. Sorry for taking over the ticket.
Can you move this under separate ticket
or i can do that for you if you wish
I got the VyOS 1.2 AMI built by Packer but it doesn't get the ssh key pulled from the metadata and stored in the configuration. With lots of manual testing I got to a stage where "/bin/cli-shell-api setupSession" fails with a core dump.
I've updated https://github.com/amosshapira/thermal to let you specify VPC ID and subnet ID required to run Packer in AWS.
Feb 2 2017
I was just going to try substitute the 1.1.7 url with the 1.2.0 url. I'm stepping through these steps manually until I can get through it. Then I can do a packer script.
How do you get the code for 1.2 into your image? I use the ISO of 1.1.7 and started work for 1.2.0 and made some progress but stopped when I hit too many problems and realised that 1.2 isn't stable (that was a few months ago).
I've just verified that the AMI gets built and runs correctly after making sure that the VPC ID and Subnet ID are set correctly in packer.json. I'll update my code when I get home. The issue to track this is https://github.com/amosshapira/thermal/issues/5
Feb 1 2017
ami-72343365 is Ubuntu official public trusty AMI in us-east-1, name "ubuntu/images/hvm-ssd/ubuntu-trusty-14.04-amd64-server-20161205" owner id "099720109477"
Hm, I can't get this command to work..
@syncer thanks for the heads up!
I will advise to work on 1.2 and not spend time on 1.1.x
For GCE just as for Azure required fresher software so 1.1.x is problematic
@amos.shapira what linux / version is this: ami-72343365 I can't find that ami.
I've used packer before, I'll go through those scripts and see if I can replicate something similar on GCE, thanks for the link!
@silverbp have you considered using Packer? I got Packer building AMI's of VyOS on AWS here: https://github.com/amosshapira/thermal/tree/master/vyos-image, perhaps you can use it as a basis for a GCE image. Let me know if you need help with understanding the code there (it uses a trick to work around Packer's lack of support for creating the final image from a "side-mounted" volume by switching volumes and rebooting).
Also as far as variations from AWS
Jan 29 2017
I'm trying to take the 1.1.7 version and get it working in GCE which I haven't had any luck so far.
I've performed the following steps: