Docker Support - CoreOS install woes
-
Hello Jeff,
Just taken a look now, I'll certainly give it a shot.
Can't believe I didn't cross this in all of my google searches.Will update this thread with the results
Thankyou.
-
To be fair, Docker support was made by Citrix in few weeks, and it's "hacky" (at best) and wasn't maintained since.
Ideally, we should do something better on our side (first in terms of general architecture, then in XO UI). It's in the backlog, but so far never make it to the actual dev process.
-
-
Hello Jeff,
Flatcar has also primarily moved to ignite but still have support for cloud-config.
Unfortunately after installation it's got Hypervisor Linux Guest Agent 6.2 which is unable to communicate with my Xen Hypervisor 8.2 installation.Further more Flatcar is shipped completely without a package manager so I'm unable to update it.
Fedoras fork of CoreOS has rpm-ostree but can't get RSA keys going just ECDSA so xs-container-prepare-vm doesn't work
I would be looking forward to such a feature, the amount of times i have to fire up a docker for a few tasks would be great to do it from XO interface.
I've had a look at that post, unfortunately they have moved away from cloud-config and moved to ignite since that forum post.
I think I'm going to revisit Fedora-CoreOS I must have made a configuration error or something I'm missing. Any other suggestions are most welcome and thanks to everyone who has replied so far.
-
@NavMan Could you explain a bit more in details the thing you'd like to have in the UI? (ideally, and functionally speaking)
-
@navman said in Docker Support - CoreOS install woes:
ignite
yeah, i think that creates a whole load of problems! It was becoming the prefered method when I got it working, but cloud-config was still possible.
So there's no way to fall back to cloud-config anymore?
-
Hello Everyone,
In the end I went with a minimal centos installation, installed Xen tools and used xscontainer-prepare-vm -v <VM_UUID> -u <username>
Really not worth doing!
Start, Stop and restart.Not sure what I was expecting but something with more control like Portainer. Your only real options with the implementation is to start, stop and restart.
Maybe see if Portainer want's to collab, that would be awesome
-
Well, that's the question: "do something like Portainer" is vague and we don't want to re-write something that's already doing the job.
So we need to prioritize, as a system admin, what would be the most used operation to do on containers without having to open portainer.
-
@olivierlambert Well for me the main things I would require start, stop, restart, console and log view.
I'm sure other people will chime in and let you know what they too would like to see in the XO UI.
-
I don't think console is possible at all (I have no idea in fact, I don't think Docker got an API to allow a remote console display). XO could deal with Docker API, it's not a "physical" access in the container.
