> On Jul 28, 2016, at 2:03 PM, Nick Owens <[email protected]> wrote:
> For the script path, try cd trunk/src/scripts.
>
> For building coreos on coreos, give this a spin:
> https://github.com/coreos/mantle/blob/master/README.md#building-coreos-on-coreos
>
> <https://github.com/coreos/mantle/blob/master/README.md#building-coreos-on-coreos>
> For pxe images, call image_to_vm.sh with --format=pxe.
>
Nick,
Thank you, this was extremely helpful!
I find building coreos on coreos is easiest...
A few more questions:
Using the coreos on coreos build script you referenced above, how do I specify
a specific release/tag of CoreOS to be built?
I see:
export V=master
cork create --replace --sdk-version=${V} --verbose
Presumably this is obtaining the latest commit of the master branch of
https://github.com/coreos/manifest <https://github.com/coreos/manifest> , is
that correct?
How would I specify a specific release?
My next step would be to actually add new files to the build.
Can you give me any pointers about what files I could modify to cause
additional files/repos to be included, built, and the resulting artifacts be
included in the build?
Thank you again,
Don
> On Jul 28, 2016 13:58, "Don Jackson" <[email protected]
> <mailto:[email protected]>> wrote:
> Hello,
>
> I'm a CoreOS newbie, FYI, I've managed to pxeboot a 4 machine cluster (bare
> metal), and get them into an etcd cluster...
>
> I'm interested in exploring/experimenting with adding some software my
> company develops into a CoreOS image,
> I am pretty sure that I cannot use a container (I need things like udev,
> etc),
> so I am attempting to build from source, and running into some issues and
> have some questions....
>
> I'm following the directions here:
> https://coreos.com/os/docs/latest/sdk-modifying-coreos.html
> <https://coreos.com/os/docs/latest/sdk-modifying-coreos.html>
>
> I built a Ubuntu 16.04.1 machine to run the build, is that an OK version of
> Ubuntu?
>
> After I run:
> cros_sdk --enter
>
> I cannot run:
> ./set_shared_user_password.sh
>
> as it is not found/there. I found it elsewhere in the filesystem, and had to
> run it like this:
> /usr/lib64/crosutils/set_shared_user_password.sh
>
> And the subsequent build commands must be path-qualified as well, e.g.
>
> /mnt/host/source/src/scripts/setup_board --default --board=amd64-usr
> /mnt/host/source/src/scripts/build_packages
> /mnt/host/source/src/scripts/build_image dev
>
> This all seems to work, AFAICT, although I haven't yet tried to run the
> resulting artifact....
>
> Questions:
> How can I generate an artifact I can pxeboot on bare metal?
>
> Why don't the paths in the docs page (referenced above) work for me?
> What am I doing wrong?
> Should I be using another version of Ubuntu, or some other environment to
> build source?
>
> Is there a way I can build CoreOS on CoreOS? (in a container?)
>
> Is there an established/documented way of building CoreOS via Jenkins?
> (I am currently thinking to turn my Ubuntu box into a Jenkins build slave and
> attempt to script the documented build process, once I get it working....)
> Any help/advice/pointers will be greatly appreciated!
>
> Don
