danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,466
So the headline news (which I guess is great news for folks who have Dockerized their infrastructure, but kind of sucks for the rest of us) is that TrueCommand is now being distributed as a Docker container. But not to worry, for those of us who haven't done this, the blog post tells us there's a .VDI disk image available to run a VM. And indeed there is--so I downloaded it, moved it into a VM under Proxmox, and booted it up.
First problem: No networking. /etc/network/interfaces specifies enp0s3, but the VM has ens18. Edited that file to specify the correct interface, rebooted, now the network is up.
Second problem: TrueCommand isn't actually running--
Is the .vdi really nothing more than a Debian installation with Docker installed and the TrueCommand image downloaded?
First problem: No networking. /etc/network/interfaces specifies enp0s3, but the VM has ens18. Edited that file to specify the correct interface, rebooted, now the network is up.
Second problem: TrueCommand isn't actually running--
docker ps
shows nothing running at all. Why would this be? Does the dedicated VM image really not have the one thing it's intended to run configured to start on boot? It seems this ought to be covered in the manual, but the manual doesn't appear to have a single word about using the disk image.Is the .vdi really nothing more than a Debian installation with Docker installed and the TrueCommand image downloaded?