May I share my successful install of TrueNAS SCALE
UDOO BOLT GEAR but I wouldn't call it stable.
- It recognizes the installed hardware (could create a zfs pool) but can't get detailed readings like temperature. I booted Ubuntu live image what was able to get all the readings
Thats unfortunate, but expected during alpha.
[*]Nextcloud app was not able to initialize due to account creation error with SQLite
To be frank, the Nextcloud app is awefull.
And Nextcloud docker containers are my main example on how not to create a docker container.
That being said: the Apps interface (and the apps) is mostly a Proof-of-Concept
[*]Launched
portainer's Profile - Docker Hub but it was not able to get access to the Docker daemon, so I tried to repeat it adding the command
Code:
-v /var/run/docker.sock:/var/run/docker.sock
in container arguments (args), what was properly the wrong place but it messed up anything. I was not able to get in running again, even with delete/reinstall.
Deploying the docker container via shell work like as usual but the container is not listed in "Applications".
Non-K8S deplotments are not supported. They are possible but not actively supported. As are adding multiple k8s management utilities. You complain about stability, but try to costumise SCALE a lot (and hence go outside of the current development scope), which i think is not fair.
That being said: Apps list SCALE apps, not all random docker containers. If you run your own docker container using docker-compose or plain docker, this is not a SCALE APP, hence is not listed as such
[*]When I go in "Application" I get numerous pop-ups that the pool cannot be read (what might be related to #1)
Might be, try rerunning the applications setup
Doing all these checks etc. raised the question, how to reports this thing properly: I cannot find a clear description of how to this, forum, but where for SCALE) or
https://jira.ixsystems.com/.
Is there a standard template, console output or log for troubleshooting?
First off: Bugs can be reported on JIRA and under config you can output a debug dump.
However: Non-supported things not-working, are not bugs
I noticed that deploying the nextcloud application includes rancher-os and Kubernetes container. Is there any intention to use Kubernetes as a standard container deployment engine?
K8S IS the standard container engine. SCALE doesn't actually officially support non-k8s docker.
(As in: official support is not provided but it "should-work(tm)" )
As docker is basically working but SCALE is UI in regard of docker ist not that useable I would try to have all containers' images, volumes etc located on zfs pool, what can be mounted into Ubuntu. That would allow me to do the same on Ubuntu to enable to run the same container on both OSs, switching easily between testing and production, as all my apps are containerized.
Any doubts/thoughts that theory could fail in practice?
The SCALE UI only lists SCALE APPS, not containers or helm charts.
SCALE APPS are specially re-crafted helm-charts, that are managed by SCALE.
If you run the setup utility from the APPS UI, it makes sure all docker images are by-default put on the ZFS pool you select.
Going back-and-forward between different OS'es however, is not actively or offically supported
Last but not least, is there any rough estimation of Alpha 21.02, there are not that many open issues open anymore.
Actually there are quite a number of things that need working, some major design tasks are not merged yet. But indeed 21.02 should launch before the end of februari. The number of issues is often less important than the scope of said issues ;-)
Anyway:
In general I find it unfair you define the product as unstable, because it doesn't want what you want it to do.
You are doing things that aren't supported and complain things don't react like you expected. This is a prime example of layer 8 issues. Not the product.