Seems a reasonable machine. OH only requires specs equivalent to an RPi 2. This machine seems way more than that.
I don’t think the Atom processor would be a problem.
It’s one of the more popular dsitros. I run it because it’s easiest to find support for stuff. You can always find an article or the like telling you how to do something or fix something in Ubuntu. But Ubuntu is based on Debian so pretty much anything that is written about Ubuntu applies to any Debian based distro. I don’t know about Clear Linux (just read about it for the first time today) but if it’s Debian based you should be fine. If not, you may need to do some translations. Its worth noting a lot of OH users also run OH on CentOS/Fedora as well. It kind of doesn’t matter really.
As for Docker, it is most certainly not OS agnostic. I’m actually not at all certain that the OH Docker instance will work on Windows, for example. But if you are running it on Linux, you can kind of think of it as being OS agnostic. But I’m not sure that’s the best way to think about it. What it is is like a great big chroot on steroids (if you know Linux that sentence makes sense, if not don’t worry about it). It provides a way for a bunch of separate environments to share the same kernel. Depending on where you draw the line on where the OS starts and stops will probably dictate whether you treat a container as OS agnostic.
I think a better way to think about it is it comes with it’s own OS except for the kernel which is shares with the host.
In what ways. I’ve been running and supporting Docker trouble shooting requests, and have even contributed a little bit to the code, for years. What may be missing is that we don’t teach you to use Docker. That’s outside the scope so you need to go “learn you some Docker” on your own.
It’s the manual install with “the directory you unzipped OH to” being /openhab2
(maybe without the 2, I don’t remember) so, for example $OH_CONF would be /openhab2/conf/. But that only really matters if you are trying to use paths from inside the container (e.g. running executeCommandLine or the like) which, if that’s a requirement, Docker probably isn’t the best choice anyway. Any time you are interacting with the files you are doing so from where ever they exist on your host usually which, I recommend using the default manual installation location (i.e. /opt/openhab2/conf and /opt/openhab2/userdata).
Anyway, back to the main topic, @Chris_K, definitely spend some time with the docs and see How to get started (there is no step-by-step tutorial) for a bunch of other getting started resources.
If you want to use a bunch of commonly used third party tools like Mosquitto, InfluxDB, Grafana, etc, you might consider the manual isntallation of openHABian on a Debian based distro (Ubuntu works). This will get you more than just OH. The Docker image is just OH.