-
Notifications
You must be signed in to change notification settings - Fork 59
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
Vagrant Cloud images for Fedora CoreOS #144
Comments
Hi @mcandre. We are not producing any OCI container images for Fedora CoreOS. For the vagrant images we have plans to create them but we don't have an estimate yet. Thanks for the interest! We'll try to have those soon. |
I found this while searching for container images for Fedora CoreOS.
@dustymabe Would you mind sharing why you aren't planning to produce these? Just curious, thanks! |
@pcgeek86 Fedora CoreOS is intended as a host operating system for running containers, not as a base image for building containers. In other words, containers run inside it, not the other way around. Do you have a use case where a Fedora CoreOS container image would be helpful? |
At the moment, I don't have a specific use case. It just seems like a common trend that operating system distributions also have a corresponding Docker image, so you can explore the environment without having to create a virtual machine. I don't use Vagrant, because on Mac you're pretty much stuck with VirtualBox, which is incredibly slow and buggy. They (Hashicorp) don't have a supported xhyve plug-in for Vagrant, which would be the most preferred option, in my mind. With that in mind, would you guys be interested in providing a tool to spin up xhyve virtual machines, similar to the It'd be neat if an equivalent tool existed for Fedora CoreOS, to ease local development and testing. |
Convenience tools of that kind aren't on our short-term roadmap, but I'm certainly in favor of making it easier to try out Fedora CoreOS. Note that Fedora CoreOS requires there to be some way to pass a userdata blob to a VM, so that users can specify an Ignition config to customize the machine. Last time I looked, xhyve didn't provide a userdata mechanism, so we'd need to investigate adding one. |
I can add a use-case: I want to use Fedora CoreOS through ignite, and locally through footloose. Ignite uses OCI-compatible images to start (micro) VMs using the AWS Firecracker project. Footloose provides the abstraction, to e.g. bootstrap the environment using docker locally, and then roll it out with Firecracker "online". I came here looking for an image to be able to spin up a test bed locally as well. Providing an image would be much appreciated. Or maybe a couple steps? I'd be happy to contribute a |
I have the same use case. I am building K8s deployment engine around ClusterAPI on baremetal with FCOS as a base image for hypervisor hosts and I really need CI environment that is as close to BM servers as possible. One of the nicest options is to spawn ignite VMs in CI and E2E tests with the target OS inside and for that we need OCI images. |
@till @stormobile your usecases are different than the initial request, it would be nice to split them to a separate ticket. In particular, you have a hypervisor/platform (
From a quick look around, I didn't find much on those topics. |
@lucab to start, we need Docker images, that's all. :) Same request. |
FCOS-in-containers in something I'd very much like to have as well :) I think this doesn't exist yet and would need a new build target for coreos-assembler |
Highly related is that cosa does build OCI containers today to ship OSTree content on OCP. Would be interesting to just repurpose that capability so that it ships a full usable tree as a hardlink-checkout of the OSTree repo. Since we wouldn't ship |
Has anyone managed to get a way to reproduce a multi-node setup locally? |
Is there any update on this at this time? I would really like to be able to setup a FCOS cluster with Vagrant for local development purposes. |
Please, if possible, dont' forget to generate Hyper-V compatible box :) |
@bgilbert To start, there are the use cases that the images "for Fedora, CoreOS, and Atomic ..." are used in.
Then, we indeed have uses with
Resources
This would allow VMs based on Lastly, one would hope that If there is a reason this is not possible currently or not desired for some reasons related to Please advise if, for the short term, is there any reason why latest |
I don't think there is any hidden reason blocking this issue here. It just needs to be worked on, tested and integrated into the CI and that takes time. |
In general, user software running in Fedora CoreOS should run in containers, not directly in the host. So the main use of a Fedora CoreOS container would be to run another container inside it. It sounds as though that'd be useful in CI for some people, so we might want to explore it. But I suspect it wouldn't be as generally useful as you're implying. In addition, Fedora CoreOS expects to be deployed as a disk image, not as a filesystem image. AFAICT there are two cases:
|
Grateful tor sharing this detailed thought process and design insights. While am digesting that, let me ask this: given what I have some interesting things to do with Hope I have not made myself too obscure... Thanks in advance. |
|
Has this become not possible with latest
Please advise. |
Not as far as I know. See https://docs.okd.io/latest/architecture/architecture.html#architecture-custom-os_architecture:
Please ask OKD specific questions at https://github.com/openshift/okd to make sure that you get the best answer. |
Much like Vagrant current support for cloud-init to provision VMs at first boot, I think we would need support for the Fedora CoreOS Vagrant images to be provisioned via an Ignition config (even if it's a default empty config with only the Vagrant insecure ssh key if nothing is provided). This would make the FCOS experience with Vagrant similar to other platforms. If you need pre-provisioned FCOS Vagrant images you should be able to create them with packer and automatic installation with the ISO installer. |
I took a deeper look at I am renaming this issue to focus on Vagrant images as this is the most concrete step forward here while other potential use cases should be tracked in other issues. |
@travier that's too bad. Again, one of the advantages of an OCI image (which is what ignite/firecracker uses) would be using Fedora CoreOS with footloose. Which I mentioned above, think local dev env or CI. Anything is faster than bootstrapping vagrant. |
While am starting/trying to see the point of not running If it is not possible atm then fine, but better to keep track of the request as formulated. |
I just hope the work is not in vain and someone actually wants to use Vagrant/Virtualbox (still). ;) |
I have created #624 to keep track of the Ignite / Footloose support request while we keep this issue focused on Vagrant support only. Thanks |
https://github.com/basvdlei/fedora-coreos-vagrant-box-builder > This projects looks like a good start for those interested in unofficial Vagrant QEMU based images. |
See #1008 for progress regarding full VirtualBox support which would make this significantly easier. |
Still very interested in vagrant-libvirt support. |
Starting with this week's releases, FCOS ships VirtualBox images. We'd still need to add Vagrant integration though. For the record, there's some old code for supporting Ignition on VirtualBox with Vagrant. It will not work as is, but some of it may be salvageable. |
Hey, how soon can we get some beta VM and Docker images published for Fedora CoreOS, so that developers can prepare their applications to run on this lean environment? I see some entries for Fedora, CoreOS, and Atomic, but no official images for Fedora CoreOS just yet.
https://app.vagrantup.com/boxes/search
https://hub.docker.com/
The text was updated successfully, but these errors were encountered: