Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[documentation] create one own images.linuxcontainers store #1581
I was wondering if there is more information about how the images.linuxcontainers.org:8443 server is setup.
I would like to create my own image store where users can grab the latest version of a specific image.
images.linuxcontainers.org:8443 is a weirdly setup apache server which pretends to be a LXD server, I'm not sure I'd recommend you do something like that youself :)
What you can do however is just run a public facing LXD server, then copy a bunch of images to it by using:
That --public flag means that the image will be accessible to "untrusted" users. Those users can add your image server with:
and then use it as you usually would:
Re I did some experimentation using some 2 vagrant boxes:
unfortunately when trying to add the lxcserver as remote in my lxcclient box it fails:
vagrant@vagrant-ubuntu-wily-64:~$ sudo lxc remote add mylxd 192.168.1.134
Does the lxd service run on port 8443 per default or should I install a nginx to host the /var/lib/lxd/images?
thanks for your help
Well I was able to setup a local LXD server when configuring lxc as specified in you last comment.
in your first comment there is an "image" keyword missing:
if one have to copy an image from one host to another the
I also had to set to an empty password on the server side:
and finally by adding a LXD remote server automatically I had to use --accept-certificate:
Note about the trust_password option: some feature would be nice to have a download channel (without password) and an upload channel (with password or key) as a minimal access control to the central LXD server.
thanks for your help again, you can close this issue!
Apologies on necroposting...
However, we don't use LXC/LXD internally (I use LXC personally, but we don't have any infrastructure that is running it). As such we don't want to run a new server (with LXD), instead it would suit us much better to use a
So is it possible to share that "weird" Apache setup? Even better if it can be adapted to Nginx!?
If we had something like that then we could just add the config to our existing webserver and provide the LXC images directly from our existing file mirror. Is that doable? Any hints on how we might achieve that?
@JedMeister so it's likely that providing a simplestreams server may be easier since it's also entirely static and just needs a bunch of json files to be placed at the right location.
Note however that whichever way you go, LXD only supports https, so you will need an https enabled web server (though with letsencrypt, it's pretty easy to get nowadays).
You can look at the simplestreams bits of our image server here:
If you publish those two files at /streams/v1/ on your image server and publish information about your image in the same format we are, you'll then be able to add this as an image server to LXD with:
And then interact with it through the usual LXD commands.