What do you think about cockpit?

There is probably overlap in the functionality of your project, and Cockpit: http://cockpit-project.org/running.html

Have you check that out?

I love when people want to reinvent the wheel…it is what the cockpit let me think…i’m kidding :wink:

This project is a bit young and in some years…maybe less…this could be interesting…but what more values that could bring to neth…it is already out of the box here

1 Like

Could be an interesting project, but as @stephdl pointed out, lets wait and see if this matures into a viable administration tool.

1 Like

@davidep has studied it and he could add more info about it

Cockpit has a beautiful architecture, tightly integrated with the underlying system and allows managing multiple servers from the same interface. It is light fast and I love the way it handles user privileges.

It is a RedHat sponsored project and comes with Fedora Server by default. In the future it can become the base for the current Server Manager, so I hope to check it out in depth soon!


This would be definitely of value for SME customers.

Great tool it would be nice to have it.

Great interview with Stef Walter
and an interesting post about The Ideals of Cockpit

I think that it should be a must-have for the new NethGUI :slight_smile:

1 Like

I repeat … somehow, you are spying on me :scream:
I had just read the interview and i had installed cockpit preview on a ns7alpha just to see it :slight_smile:
(btw the container section seems nice)

1 Like

ahahah no dude, really! No spyware installed :smiley:

and? How it looks?

yeah i know, i know :slight_smile:

looks nice, and it works also with multiple ns7alpha…
if you want to try it on ns7alpha:

$ wget https://copr.fedoraproject.org/coprs/g/cockpit/cockpit-preview/repo/epel-7/msuchy-cockpit-preview-epel-7.repo
$ cp msuchy-cockpit-preview-epel-7.repo /etc/yum.repos.d/
$ yum install cockpit

$ config set fw_cockpit service TCPPort 9090 access public status enabled 
$ signal-event firewall-adjust
$ systemctl start cockpit.socket
$ systemctl enable cockpit.socket
$ systemctl start docker
$ systemctl enable docker    


ah… and changing hostname from ns webui seems to change the transient hostname and not the Static hostname…

edit: updated service key as suggested


Hi @dz00te, great shot!

Did you also try the version from extras repository?

I installed cockpit-0.77-3.1.el7.x86_64

On your command list I’d add fw_ to the service key, to be compliant with http://docs.nethserver.org/en/latest/third_party.html#firewall

config set fw_cockpit service TCPPort 9090 access public status enabled

WOW, successfully started a nethserver/docker-demo container from Cockpit :heart_eyes:

You’re making me extremely curious :frowning:

I would like to revive this discussion and have (another) serious look at cockpit. I just think it is AMAZINGLY easy to use and if you want to add an extra feature to your server, just look at the docker repository and it is 1 click away.

I am going to try this on both Ubuntu (Karoshi and Zentyal server) and CentOS (NetServer) servers the coming weeks.

Of course, since it is so easy to add and use, it could be installed just on a NethServer, but a real integration would be an admins wet dream… :wink:


Een bericht is gesplitst naar een nieuw topic: Install cockpit on NethServer 7b2

Any experience with cockpit is welcome! I’ll join your initiative ASAP after ns7 Final release!

1 Like

I reply here regarding the e-smith layer and its implications
In cockpit, when you change a parameter (for example IP address) the change is in real time, just like you do via CLI
In NS, when you change a parameter, its value is stored into a database and one or more events is/are triggered, making all involved services work in a transparent manner
In cockpit, when you change a valute, almost no service is aware of the change

So the conclusion of this phenomenon is that you stay off any settings of the NethServer you run Cockpit on and only use it to easily deploy docker containers? Or would there still be options to manage the local NethServer (and maybe multiple remote NethServers)?

thnx anyway for this clear comment. It points exactly to the power and limitations of Cockpit.

I guess that the disk management panel of cockpit can help also

1 Like

I’d like to give cockpit a try too! Thanks to @robb for his effort and @Stefano_Zamboni for explanations
We should bear all this in mind :slight_smile: