acbuild examples break on coreos vagrant example

[jdu]

This might be my own stupidity, but I'm trying to learn how to use acbuild for a project and I'm running into an issue.

I'm submitting this as an issue as there are probably going to be a few people who are coming along the same learning path as I am (or already have and might have given up)

To outline the path I've taken to do this I've detailed my steps here:

1. OK - Read through https://coreos.com/rkt/docs/latest/trying-out-rkt.html and set up the vagrant mentioned in the article
2. OK - Did this tutorial https://github.com/coreos/rkt/blob/master/Documentation/getting-started-guide.md

So I can get a statically built Go application running, but my applications are running on python (predominantly). So I need to do a bit more work to the ACI than the basic Go application example.

So I started with this one:

https://github.com/appc/acbuild/blob/master/Documentation/getting-started.md

I'm somewhat familiar with alpine, but this is where I started running into problems.

My first run I got to:

acbuild run -- apk update

and it told me I needed to be running as root. So I acbuild end and do su - and swap to root inside the vagrant.

I restart the acbuild instructions from the tutorial and when I get to acbuild --debug run -- apk update I get the following:

Running: [apk update]
Downloading quay.io/coreos/alpine-sh: [========================] 2.65 MB/2.65 MB
run: exec: "systemd-nspawn": executable file not found in $PATH

after that, the next step is acbuild run -- apk add nginx which if I continue on, produces the same error.

Now, these are the potentials:

1. There's something wrong with the coreos/rkt vagrant and it doesn't work with the acbuild/examples
2. There's something I'm missing (or is missing from the acbuild examples that needs to be clarified)
3. There's something wrong with quay.io/coreos/alpine-sh:latest

Any help would be greatly appreciated and I think would help anyone else who is probably coming along this path from rkt documentation to here, I'm not sure if it's something i've missed or there needs to be a bit more info in the examples or there's something wrong in the setup chain I've gone through.

As an aside -- Is there an IRC channel or anything up anywhere?

[cgonyeo]

1. There's something wrong with the coreos/rkt vagrant and it doesn't work with the acbuild/examples

This is the most likely problem here. I'll look into switching the image to use a distro that has systemd-nspawn in it, just need to find someone with a working vagrant install. Thanks for reporting this.

And there are IRC channels (all on freenode):

• #rkt: for talk relating to rkt
• #rkt-dev: for talk related to rkt development
• #coreos: for talk relating to anything CoreOS (there's far more activity in here than the other two)

[foxx]

I'm getting this same problem, and this is after having running apt-get install linux-image-4.2.0-18-generic. Seems this is because 14.04 does not have systemd, however 16.04 in Vagrant is currently broken due to outstanding bugs for the last 3 months, see here

vagrant@vagrant-ubuntu-trusty-64:~/lol$ sudo acbuild --debug run apk update
Running: [apk update]
Downloading quay.io/coreos/alpine-sh: [========================] 2.65 MB/2.65 MB
run: exec: "systemctl": executable file not found in $PATH

vagrant@vagrant-ubuntu-trusty-64:~/lol$ uname -a
Linux vagrant-ubuntu-trusty-64 4.2.0-18-generic #22~14.04.1-Ubuntu SMP Fri Nov 6 22:20:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

vagrant@vagrant-ubuntu-trusty-64:~/lol$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS

[kaustavdm]

Trying for the first time today, I hit the same problem on Ubuntu 16.04 and I had to install the systemd-container package. So, apt-get install systemd-container solved it for me. Though I am not sure the cause of the issue mentioned by @jdu is the same as mine.

[taqtiqa-mark]

Note that systemd-container package and systemd-nspawn do not appear to be available in a Trusty host/build environment. You are likely to see something like this issue when you try to run somthing like acbuild --debug run apk update which are the commands this issue relates to

HTH someone.