Mathieu Tortuyaux

hello and sorry, I was totally unaware of the recent conversation here. With this repository comes a natural question: what's the limit for proposed software? In this specific case: >...

Hello, thanks for this detailed issue and happy to see the interest of using Flatcar on Anexia. Usually, the providers OEM are maintained in the scripts repository (see there: https://github.com/flatcar/scripts/tree/main/sdk_container/src/third_party/coreos-overlay/coreos-base...

Hi @LittleFox94, Something I have been thinking - since this OEM image would be out-of-tree, I think we could consider it as a regular sysext image and then leverage the...

Tested a Flatcar OpenStack image on Brightbox, it works fine - including Ignition and Afterburn. Sent a PR (https://github.com/brightbox/gobrightbox/pull/39, https://github.com/brightbox/gobrightbox/pull/40) to allow image creation from the Go SDK in order...

Hi @Weldawadyathink and thanks for the report, From a first look this usually means that there is an issue with Ignition: ``` [ 5.068506] BTRFS info (device vda6): last unmount...

I added IPV6 support to Ignition and it confirms the guess: ``` INFO : GET http://169.254.42.42/user_data/cloud-init: attempt #27 INFO : GET error: Get "http://169.254.42.42/user_data/cloud-init": dial tcp :45->169.254.42.42:80: connect: network is...

@Weldawadyathink thanks for asking but nothing you can do on your side at this moment. I'll work on an Ignition patch to implement this, the best thing you could do...

Hello @Weldawadyathink would you be happy to try this image to see if it works with IPv6 only: https://bincache.flatcar-linux.net/images/amd64/9999.0.0+tormath1-ignition/flatcar_production_scaleway_image.qcow2 ? It comes from this PR: https://github.com/coreos/ignition/pull/2052

> Happy to test [@tormath1](https://github.com/tormath1) ! > > I followed the same process as in the documentation (upload to object storage, load as snapshot, create instance from that snapshot). I...

> I included an ignition.json, with some references to http resources. It was the same ignition file as I used in the original bug report (or at least the same...