I can download Stream metadata for the next stream under the URL
https://builds.coreos.fedoraproject.org/streams/next.json
but there is no corresponding URL for the rawhide stream:
https://builds.coreos.fedoraproject.org/streams/rawhide.json
Shouldn’t there be one?
It would make it easier to try out the rawhide builds.
(I understand that the rawhide stream is experimental and not supported)
$ curl -s https://builds.coreos.fedoraproject.org/streams/next.json | head -5
{
"stream": "next",
"metadata": {
"last-modified": "2021-06-29T10:21:47Z"
},
$ curl -s https://builds.coreos.fedoraproject.org/streams/rawhide.json | head -5
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>34JBQ0V9EMCP9CF9</RequestId><HostId>ptbFDVVaCSvT9birawsztm0XMqs2hSYGmobP4vjUrh1Yrj3tZ6xd9pJMNScUuaR0LRcMebW2Ivk=</HostId></Error>$
bgilbert
(Benjamin Gilbert)
July 3, 2021, 9:49pm
2
Mechanical refs intentionally don’t have stream metadata. That was an early design decision, and we could revisit it. But note that those refs don’t undergo any package curation at all, so they’ll likely be less functional than the nightly builds of our development branches.
I would be interested to use rawhide (or the nightly builds of the development branches) in
I managed to boot Fedora CoreOS with vboxmanage (a VirtualBox command) from a Butane config in a GitHub Action. It’s more of a proof-of-concept right now. If anyone is interested: https://github.com/eriksjolund/fedora-coreos-vm/commit/052fb7bcbcea9831601e994cef9e6fc2ea12ea8e
As I understand it the VM is running hardware accelerated.
I’ll try to clean up the code during the coming weeks. The original code came from
Here is a sketch of the architecture:
Download metadata for the stream
Extra…
One input parameter to that GitHub Action is the name of the stream (stable , testing or next ).
The metadata JSON is then downloaded from
const json_url = `https://builds.coreos.fedoraproject.org/streams/${stream}.json`;