New Container templates

[Ala de Dragon]

Hello I just arrive to the community.

I want to deploy a few containers witch are not in the PVE default list.

All of them are located in LXC repos:

http://us.images.linuxcontainers.org/
devuan beowulf amd64 cloud 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf amd64 default 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf arm64 cloud 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf arm64 default 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf armel cloud 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf armel default 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf armhf cloud 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf armhf default 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf i386 cloud 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO devuan beowulf i386 default 20200924_11:50 YES (1.0 and up) YES (1.0 and up) YES NO

What is the proper way to add them to my local instalation of PVE?
Thak you so much

 

[t.lamprecht]

Hi.

You can always manually download and then upload any Container template to a storage and use it then.

The prebuild one come partially from us, Debian and derivatives through the dab, with the configurations in the dab-pve-appliances repository, Arch Linux through our Arch Linux appliance builder (AAB) the rest comes mostly directly from lxc templates, is signature verified and tested by us and uploaded in our CT appliance repository

Actually we had a build for the first Devuan, then Jessie - https://git.proxmox.com/?p=dab-pve-...52777e1675a71e34c178272fb61e773ece919;hb=HEAD

So a build for Beowulf could be possible, but isn't it already EOL? At least the Debian counterpart "stretch" got EOL in July.

 

[Ala de Dragon]

Hello, I'm fairly new to container so I will investigate each piece of information you provided me. Is the first time I try to run containers.

Devuan 3 (Beowulf) is based on debian 10 (buster) and attending to Debian site will EOL in 2022, there are testing and unstable versions but this

Is the current stable build.

10

Buster

2019-07-06

~2022

Maybe will be a bit of effort for the pve team, but if you teach me a bit I can help testing/working on the devuan release. I'm active in Devuan forums user as well.


For example, I was able to export a image container with the command:

lxc image export images:devuan/beowulf /var/snap/lxd/common/lxd/storage-pools/default/images/devuan_beowulf -v

Now I have to files in the export dir:

ls -la /var/snap/lxd/common/lxd/storage-pools/default/images/
total 89168
drwx--x--x 2 root root     4096 Sep 25 11:06 .
drwx--x--x 9 root root     4096 Sep 25 10:28 ..
-rw-r--r-- 1 root root      672 Sep 25 11:06 devuan_beowulf
-rw-r--r-- 1 root root 91295744 Sep 25 11:06 devuan_beowulf.root

Reading the info you wrote, I found this file in proxmox git:

https://git.proxmox.com/?p=dab-pve-...ain;f=devuan-1.0-standard-64/dab.conf;hb=HEAD

And this file is related to Devuan version 1.0 witch effectively is in EOL.

So having a look to the file I noticed a few artifacts:

Suite: devuan-jessie
CacheDir: ../cache
Source: http://auto.mirror.devuan.org/merged SUITE main contrib
Source: http://auto.mirror.devuan.org/merged SUITE-updates main contrib
Source: http://auto.mirror.devuan.org/merged SUITE-security main contrib
Architecture: amd64
Name: devuan-1.0-standard
Version: 1.0
Section: system
Maintainer: Pasquale Fiorillo <info@pasqualefiorillo.it>
Infopage: https://devuan.org
Description: Devuan 1.0 (standard)
 A small Devuan Jessie system including all standard packages.

There was a update in server name space in Devuan, I don't know if the URI in file was affected by the change but if I remember properly instead of deploy a round service in old debian style, looking for the nearest/fastest repo for you, they use now load balancers with CDN and geolocation to direct your ip to the nearest fastest mirror (That is just my "felings" but we can check with Devuan team if needed). Anyway if you try to browse to:
http://auto.mirror.devuan.org
redirects to:
http://packages.roundr.devuan.org/merged
And it fails, so IMMHO the uri can set to:

https://pkgmaster.devuan.org/merged/

wich is the standard repo now.


I suppose that HTPS is allowed, if not just move into http instead.

the final file can be something like this:

Suite: beowulf
CacheDir: ../cache
Source: https://pkgmaster.devuan.org/merged/ SUITE main contrib
Source: https://pkgmaster.devuan.org/merged/ SUITE-updates main contrib
Source: https://pkgmaster.devuan.org/merged/ SUITE-security main contrib
Architecture: amd64
Name: devuan-3.0-Beowulf
Version: 1.0
Section: system
Maintainer: Pasquale Fiorillo <info@pasqualefiorillo.it>
Infopage: https://devuan.org
Description: Devuan 3.0 (Beowulf)
A small Devuan Beowulf system including all standard packages.



Since is my first contact with containers maybe a hack will be needed in order to make run in a proper way.
Thanks for your comments.

 

[Vazhnov]

Try these instructions: pve-devuan-appliances to easily build any Devuan version you want.
Also there are a ticket to prevent using workaround:

echo ascii > /etc/devuan_version

 

[Ala de Dragon]

Thank you. I'm following the bug traker and Github link