TrueCommand 1.2 now available!

[PantACRO4life]

ok so I start over fresh install centos and docker from

curl https://releases.rancher.com/install-docker/19.03.8.sh | sh

and still the same

 

[PantACRO4life]

that link my bad https://github.com/rancher/install-docker

 

[PantACRO4life]

ok that is way not the easiest setup at all been trying for 5 hour and nothing work stuck at the login screen ....



[root@TrueCommand]# docker info
Client:
Debug Mode: false

Server:
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 2
Server Version: 19.03.8
Storage Driver: overlay2
Backing Filesystem: <unknown>
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-1062.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 5.669GiB
Name: TrueCommand
ID: E3TX:T53E:HUOJ:C47W:HGG4:KSFG:AUSN:MKXI:J2QG:7SJF:IO75:4EC4
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

[root@TrueCommand]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
81def3e8b2c6 ixsystems/truecommand "/start.sh" 9 minutes ago Up 9 minutes 0.0.0.0:8080->80/tcp, 0.0.0.0:8081->443/tcp xenodochial_shtern
[root@TrueCommand]# docker version
Client: Docker Engine - Community
Version: 19.03.8
API version: 1.40
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:27:04 2020
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:25:42 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
[root@TrueCommand]#

 

[jon.z]

@

ok that is way not the easiest setup at all been trying for 5 hour and nothing work stuck at the login screen ....
...

For what it's worth, we're having the same issue when trying to run latest TrueCommand container (1.2.2) on a Docker Swarm hosted on Centos 7 VMs. The issue appears to be a Qt shared library requiring a later Kernel version than Centos currently offer, according to this and this. So much for portability of a container..

# uname -a
Linux mn2-dev 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

# docker service logs
...
XXXXX | 2020-04-20 23:35:30,766 INFO exited: middleware (exit status 127; not expected)
XXXXX | 2020-04-20 23:35:30,766 INFO gave up: middleware entered FATAL state, too many start retries too quickly
docker exec -it -u 0 660e27db3497 /bin/bash
root@660e27db3497:~# cat /var/log/ix_middleware.log
/usr/bin/ix_middleware: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
/usr/bin/ix_middleware: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
/usr/bin/ix_middleware: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
/usr/bin/ix_middleware: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
root@660e27db3497:~# ls -lha /usr/lib/x86_64-linux-gnu/|grep libQt5Core
lrwxrwxrwx. 1 root root 20 Jan 30 13:42 libQt5Core.so.5 -> libQt5Core.so.5.11.3
lrwxrwxrwx. 1 root root 20 Jan 30 13:42 libQt5Core.so.5.11 -> libQt5Core.so.5.11.3
-rw-r--r--. 1 root root 5.0M Jan 30 13:42 libQt5Core.so.5.11.3
root@660e27db3497:~#

 

[jon.z]

Just to follow up, I upgraded the kernel only on our Development Centos 7 VM in a Docker Swarm and ran the TrueCommand 1.2.2 container - success. However, upgrading the Kernel version across our fleet to run TureCommand is not a real fix unfortunately. Devs, is this something you can address in a new release?

Code:

uname -a
Linux mn2-dev 4.4.219-1.el7.elrepo.x86_64 #1 SMP Sun Apr 12 16:13:06 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
docker service logs XXXXX
XXXXX    | 2020-04-21 02:20:16,550 INFO success: middleware entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)

 

[KevDog]

@Kris Moore
Are there any ENV options I can pass to the container?
In addition is there a method where I can use Let's Encrypt Certs for the container and mount the certs as volumes into the container?

After installing docker image (which was really easy) and probing around in the container, I just have a few questions
1. As mentioned above - process to stop the generation of self-signed certificates and install external certs
2. Timezone settings
3. Email Notifications?
4. Ability to proxy_pass to the upstream freenas installations via https rather than http. I read the commend regarding use of self signed certs in the middleware, however if you have installed valid SSL certs within freenas, can those be utilized?

All in all truecommand reminds me of a primitive Xen Orchestra implementation. It would great if TrueCommand offered a shell window into the individual freenas installation.

 

[danb35]

offered a shell window into the individual freenas installation

Only if that shell window is much better than what's built in to FreeNAS right now.