During work building Docker executables, I ran in an interesting corner case.
Fortunately the Docker IRC channel helped me to investigate with special credits to Ravensoul.
When you build a container as an executable you can use the ENTRYPOINT for your binary to execute and CMD as a default overwritable argument.
In most cases the CMD is the --help argument to provide a useful default behavior in case you just run the container without anything specified.
I’m using Mac OS X with iterm2, oh-my-zsh and spend 75% of my time in those terminals.
It is totally annoying to me if I connect to a DHCP network and it screws up my hostname.
Especially when I’m used to looking at the prompt which tells me the host I’m connected to.
It is possible to fix your computer name for several things using the scutil command which requires administration permissions.
I’ve found a link to the Mac OS X Server Worksheet which explains a few things in more detail.
Here is what I did to prevent my computer changing the host name.
We are all happy when we are able to get IPv6 connectivity for our new servers.
In case the network is provided by someone else and some kernel settings you can get in some tricky situations.
With IPv6 there are so many addresses your Laptop and Mobile can have a unique public IPv6 address forever - pretty cool huh?
The downside is, it would be pretty easy to trace every connection you ever do back to your device - this really not what you want!
When you provide a service this behavior is not so useful.
Otherwise there are several ways to autoconfigure your IPv6 configuration, beside DHCPv6 the interesting one is stateless address configuration.
If you run a centralized monitoring system in large environment you can run in some issues regarding file descriptor limits. Linux gives you very detailed information in the kernel control and information center in /proc. The soft and hard limits have effect for file and network sockets, which can end up in a too many files open exception in OpenNMS.
The default values for soft and hard limits can be checked with
If you have OpenNMS with RRDtool running, you can improve the whole rendering a little bit just by replacing the command.prefix in the following files:
I don’t like the stamp size graphs in OpenNMS, so I changed it for all.
It could be problematic if you have grouped graph report (KSC report).
So if you have trouble, you can just remove the –width and –height parameter.
The command will also overwrite the width and height for all graphs, so they have all the same size.
You have to be careful if you have KSC reports with multiple columns.
If you have RRDtool running, you can improve the graphs with anti-aliasing using a few additional parameters:
cd ~/Pictures
wget http://files.opennms-edu.net/wallpaper/free-software-ulf.jpg
cd /usr/share/backgrounds
wget http://files.opennms-edu.net/warty-final-ubuntu-ouce.png
sudo -i
xhost +SI:localuser:lightdm
su lightdm -s /bin/bash
gsettings set com.canonical.unity-greeter draw-user-backgrounds 'false'gsettings set com.canonical.unity-greeter draw-grid 'false'gsettings set com.canonical.unity-greeter background '/usr/share/backgrounds/warty-final-ubuntu-ouce.png'