We're having a Cockpit hack fest at the http://devconf.cz/ 2014 in Brno.
When: Friday February 6, 2014 at 14:10-17:10
Location: Room A113, Brno University of Technology, Brno, CZ
We'll be helping folks figuring out how to hack on Cockpit, building
some plugins or prototypes, and doing general scheming. If you want to
get your feet wet (or dirty) this is the place to be.
Devconf does not require an admission fee. Just come: http://devconf.cz
Packagers of Cockpit might be interested in this pull request. We'll
start to describe our dependency on GLib more accurately. Since versions
of GLib before 2.37.4 crash with cockpit-ws, we'll refuse to build on
This is the bug in question:
However if your distro has patched GLib to fix this bug (I think CentOS
has done this), you can use the mechanism provided by pkg-config to
override the check in question. This is described in the failure output
of configure when this dependency are not met:
> Alternatively, you may set the environment variables GLIB_TLS_CFLAGS
> and GLIB_TLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
Some people have asked (on IRC and in private emails) to see the Cockpit
multi-host dashboard work, which includes some Kubernetes data.
The goals of the dashboard are to answer and or help with:
* What are my servers doing, and what is their health?
* Did anything noteworthy happen since I last looked?
* Quickly jump to the detailed view of a server and/or service.
* Quickly correlate basic info of what is where, and where did
Here's a screenshot with some explanations:
Pull request is here:
This is work in progress, but it actually mostly works ... lots of
testing ... continuous integration setup ... polish needed before it can
Hi folks, I'm working for Parallels. Cockpit is really promising tool.
We are interested in adding OpenVZ and Parallels VM/CT support to cockpit project.
Is possible to have a call and discuss this option?
I did a bit of a proof of concept for Cockpit showing a GUI remotely
using noVNC. noVNC is a nice HTML5 VNC implementation. This is wrapped
up as a Cockpit plugin ... and Cockpit provides the WebSocket,
authentication, and all of that. It's very raw at this point ... but in
case it piques anyone's interest. Screenshot:
My current work on this will go as far as polishing up this pull request
into Cockpit code example:
Information on installing/creating plugins here, which you'll need to
understand if you want to try this out. You'll also need Cockpit from
git master, or wait until the next 0.34 release.
If someone has solid interest into building this into a full Cockpit
feature, then they can work with the Cockpit team to prototype, plan
(with use cases), design (with our designer: Andreas) and implement such
Come to #cockpit or cockpit-devel(a)lists.fedoraproject.org
Features built into Cockpit are expected to work out of the box and be
discoverable. But I think that's within the reach of such a VNC based
"access-a-gui-installer-remotely" use case, if someone puts enough time
We're working on using PCP to load server resource metrics in Cockpit.
Is it possible to build pcp-libs without libavahi? It seems an odd
feature for such a low level library to have ... as opposed to higher
level PCP tools ... where dynamic discovery is interesting.
cockpit-bridge is the piece of Cockpit proxies requests from the
Cockpit Web a component we want to have as few barriers as possible.
It's part of Cockpit that we want to be able to be installed on as
many servers as possible. So we have to take a hard look at every
single cockpit-bridge dependency, even the ones we currently have...
Can we have /usr/lib64/libpcp.so without an Avahi dependency? Or
should we treat PCP as an optional dependency of Cockpit and structure
our code so that PCP is more of an add-on, used when available?
What do you think?
-----BEGIN PGP SIGNED MESSAGE-----
On 28.11.2014 00:45, Tim Moor wrote:
> Hey Stef, this is a pretty basic question, but seeing as I am new
> to FC21, Cockpit and it's integration with Docker I need a bit of
I hope it's okay if I CC the response to the mailing list.
> I've got a clean install of FC21-BETA and while pocking around I
> came across the container management section. However despite
> apparently having 'Contain Administration' roles I'm still being
> prompted with an authorization error.
> Any ideas?
> Error: Not authorized to access Docker on this system
Did you log out and back in after adding 'Container Administration'?
You can double check if you have the Container Administration group by
looking for 'docker' listed in the command here:
When logged in as the same account (not root) via SSH, can you run
docker commansd do you get a failure there too?
$ docker ps
What does the following command output:
$ ls -l /var/run/docker.sock
Hope that helps.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----