[Container-tools] "atomic projectatomic/helloapache" UX feedback

[Tomas Radej]

Hi.

On 21/05/15 07:01, Nick Coghlan wrote:
> Since I got a new personal laptop recently that didn't have *any* of
> the container tech installed yet, I decided to take a look at the
> "What's the UX like when you do it wrong?" experience for the Nulecule
> helloapache app. System is running the F22 beta release.
>
> I also figure I only get one shot at being a complete Nulecule noob,
> so I may as well make the most of it :)
>
> I'm posting my observations here initially in order to get feedback on
> what's a bug, what's an RFE, and what I should just turn into a PR for
> the helloapache example (e.g. adding a "Prerequisites" section to its
> README)
>
> Example I'm (mostly) following:
> https://github.com/projectatomic/nulecule/tree/master/examples/helloapache
>
> 1. I took "yum install atomic" as implied. All good :)
>
> $ rpm -qa atomic
> atomic-0-0.7.gita7ff4cb.fc22.x86_64

DevAssistant will/should be able to take care of this once it's 
integrated with Nulecule. It can bring in atomic, Docker, kubectl, 
whatever you need.

> 2. "atomic run projectatomic/helloapache" fails cryptically and sudo
> doesn't help:
>
> $ atomic run projectatomic/helloapache
> ('Connection aborted.', error(2, 'No such file or directory'))
> $ sudo atomic run projectatomic/helloapache
> [sudo] password for ncoghlan:
> ('Connection aborted.', error(2, 'No such file or directory'))
>
> 3. Guess likely cause as being the docker daemon not running:
>
> $ systemctl status docker.service
> ● docker.service - Docker Application Container Engine
>    Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled;
> vendor preset: disabled)
>    Active: inactive (dead)
>      Docs: http://docs.docker.com
> $ systemctl start docker.service
> (This prompted me to escalate privileges appropriately, rather than
> just failing)

Also solvable with DevAssistant.

I'll post a separate mail with my idea of what all DevAssistant can do 
for Nulecule.

Regards, Tomas