Re: [atomic-devel] Atomic including cockpit-bridge?

[Stef Walter <stefw redhat com>]

On 26.02.2015 23:31, Colin Walters wrote:
> *zoop, thread necromancy*
> 
> On Thu, Dec 4, 2014, at 11:54 AM, Stef Walter wrote:
>>
>> I'd like to see if we can get part of Cockpit into Atomic proper:
> 
> That'd be cool.  I am looking at this again because
> Fedora 22 Cockpit pulls in PCP which pulls in a world of Perl,
> and PCP also has lots of regular files in /var which is incompatible
> with the OSTree state model.  

That was temporary. Cockpit 0.40 no longer does this. PCP is now an
optional dep. See:

https://lists.fedorahosted.org/pipermail/cockpit-devel/2015-February/000265.html

>>  * The cockpit-bridge which proxies UI requests to the system
>>  * The Atomic specific Cockpit UI files
> 
> In other words,
> 
> --- a/fedora-atomic-docker-host.json
> +++ b/fedora-atomic-docker-host.json
> @@ -51,7 +51,8 @@
>  		 "policycoreutils-python",
>  		 "setools-console",
>  		 "audit",
> -		 "cockpit",
> +		 "cockpit-bridge",
> +		 "cockpit-docker",
>  		 "kubernetes", "etcd", "cadvisor",
>  		 "flannel",
>  		 "docker-io",

At present you need:

cockpit-bridge   (the bridge)
cockpit-shell    (UI files)
cockpit-docker   (UI files, in own package since docker x86_64 only)
cockpit-daemon   (legacy stuff we're moving away from)

Unfortunately cockpit-daemon (a legacy component from our prototype
days) drags in a number of dependencies that we don't want going
forward. Work is underway to it, and make its dependencies optional:

https://github.com/cockpit-project/cockpit/issues/1679
https://github.com/cockpit-project/cockpit/issues/1853
https://github.com/cockpit-project/cockpit/wiki/Storage-Refactor
https://github.com/cockpit-project/cockpit/issues/1681

We've dropped two dependencies in the last two releases ... so there is
progress here. FWIW, these dependencies are already in Fedora Atomic ...
but we want to resolve that.

> I had a chance to test this out locally today.  I started out with
> a F21 Atomic Cloud VM, rebased it to a locally generated F22 tree (which worked btw),
> then:
> 
> $ sudo docker run --privileged -v /:/host -d stefwalter/cockpit-atomic:wip
> $ sudo docker logs ecstatic_kirch
> cockpit-run: refusing to run on host with cockpit already installed
> $ rpm -q cockpit
> package cockpit is not installed
> $ rpm -q cockpit-bridge
> cockpit-bridge-0.39-1.fc22.x86_64
> 
> Is there a newer image you could push?

Yes, I would likely need to do that. In particular our protocol is not
stable yet. So having different version of cockpit in the host and the
container won't work yet. That's a goal for Fedora 22:

https://github.com/cockpit-project/cockpit/milestones/Protocol%20Cleanup

Will try to get something ready here. Do you have a way of pushing your
work tree with the above, so I can pull it and diagnose the issue?

Stef