Hi Don,

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

For pxe images, call image_to_vm.sh with --format=pxe.

On Jul 28, 2016 13:58, "Don Jackson" <[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
>
> 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:
>
>    1. How can I generate an artifact I can pxeboot on bare metal?
>
>    2. 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?
>
>    3. Is there a way I can build CoreOS on CoreOS?  (in a container?)
>
>    4. 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
>

Reply via email to