Running Eclipse Che Easily on Fedora 25

Running Fedora 25 and want to give Eclipse Che a test spin? It’s far easier than you may think.

  1. Install Docker
  2. Install Che
  3. Run Che

The steps are simple but quite important they are followed closely. Best to always follow the official process, right? In that spirit, the instructions for getting Docker running on Fedora were quite straightforward. Use those to make sure you’re running Docker smoothly.

As advertised on its homepage, getting Che installed is as simple as a single command: docker run eclipse/che start

Next comes the simple but tricky part. On Fedora 25 I figured out that I couldn’t use the shortened Docker command – I needed to run the full explicit one specifying paths. I didn’t want to have to remember this, and I also wanted to make sure Docker was running whenever I needed to run Che, so I created the following bash alias to use:

alias che='sudo systemctl start docker && sudo docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /home/ennenine/Development:/data eclipse/che start'

Now whenever I want to spin up Che and start working, I simply have to type che into the nearest terminal.

Hiding Application Icons in Wingpanel on Elementary

Elementary OS Loki looks beautiful, though I do find myself annoyed with the extra application icons that show up in wingpanel in the upper-right of the screen:

Before

In order to get rid of them you need to edit ayatana.blacklist to include the Id of the applications you want to restrict from showing up there. To start with, take a look at what is already in yout blacklist. To see its contents run the following Terminal command:

Mine originally looked like this:

Next, we’ll find the Id of applications you want to restrict. Be sure they are not already running. We’re going to start dbus-monitor and launch our apps, watching for when they register with dbus. Because there is a lot of text output, save it to a file you can search afterwards.

In the Terminal enter the following command:

This will create a text file called dbus-monitor.txt and stream all of the output from the dbus-monitor command in to it.

Next, launch your application. When it is finished launching, go back to the terminal and type control-c to cancel the dbus-monitor command. Then launch a text editor and load the dbus-monitor.txt file.

Search for string "Id". The first result that comes up should be the entry for your application. In this case, you can see from the screenshot that the Id for the OwnCloud sync client I launched is ownCloud. The Id is case sensitive so be sure to pay close attention.

dbus-monitor.txt

Edit your ayatana.blacklist and place the Id values for any applications you want to restrict in a new line of the file. I added an entry for the OwnCloud sync client and f.lux so now my file looks like this:

Save the file, and log out. Next time you log in your restricted applications will no longer be displayed in wingpanel. Sometimes it takes a few trials to get this right as there may be a few different Ids in use by the application. If it doesn’t work, try searching the dbus-monitor.txt file again and see if there are other Id values you could try.

After