Hello,
I would first like to thank the Proxmox team for their excellent software.
I have a particular use-case of PVE, and I hope this is the correct place to address my issue.
I work for a company where we use PVE in an offline environment due to security concerns.
We have adopted the use of containers, which have proven to be very useful due to them being highly automate-able.
We use a single Proxmox sever as the basis for some of our laboratories, and in particular the image centos-7-default_20161207_amd64.tar.xz which seems to no longer be available at download.proxmox.com/images/system (CentOS 7.2 based)
In order to customize the installation, we perform the following steps:
Right now, we are working around the issue by using CentOS-7-x86_64-Everything-1704.iso ( CentOS 7.4 ) which has newer packages with respect to the latest centos-7-default_20170504_amd64.tar.xz.
To me, an easy-fix would be that the Proxmox team, release their container templates based-on the official CentOS release ISO which is released yearly WITHOUT any updates. It would also be very neat if instead of date-codes such as 20161207, the releases would be aligned with the CentOS year-month codes such as 1704. Again, this is primarily for OFFLINE users of PVE and CentOS. This would bring it more in-line with the format used for debian and ubuntu at download.proxmox.com/images/system which seems to be more consistent for release-based distros, rather than rolling-release distros such as gentoo or arch.
If for whatever reason, the Proxmox team, does not share this point-of-view, then it would be nice if the scripts/environment/guide used to generate the centos container template were shared on git or wiki for example, so customers would be able to generate their own images for use in PVE according to whatever their requirements are.
Thank you,
Vittorio Alfieri
I would first like to thank the Proxmox team for their excellent software.
I have a particular use-case of PVE, and I hope this is the correct place to address my issue.
I work for a company where we use PVE in an offline environment due to security concerns.
We have adopted the use of containers, which have proven to be very useful due to them being highly automate-able.
We use a single Proxmox sever as the basis for some of our laboratories, and in particular the image centos-7-default_20161207_amd64.tar.xz which seems to no longer be available at download.proxmox.com/images/system (CentOS 7.2 based)
In order to customize the installation, we perform the following steps:
- Create container machine using pct in a bash script
- Mount official CentOS-7-x86_64-Everything-1611.iso ( CentOS 7.3 ) in the container
- Install missing packages required for our laboratories from the Everything ISO.
Right now, we are working around the issue by using CentOS-7-x86_64-Everything-1704.iso ( CentOS 7.4 ) which has newer packages with respect to the latest centos-7-default_20170504_amd64.tar.xz.
To me, an easy-fix would be that the Proxmox team, release their container templates based-on the official CentOS release ISO which is released yearly WITHOUT any updates. It would also be very neat if instead of date-codes such as 20161207, the releases would be aligned with the CentOS year-month codes such as 1704. Again, this is primarily for OFFLINE users of PVE and CentOS. This would bring it more in-line with the format used for debian and ubuntu at download.proxmox.com/images/system which seems to be more consistent for release-based distros, rather than rolling-release distros such as gentoo or arch.
If for whatever reason, the Proxmox team, does not share this point-of-view, then it would be nice if the scripts/environment/guide used to generate the centos container template were shared on git or wiki for example, so customers would be able to generate their own images for use in PVE according to whatever their requirements are.
Thank you,
Vittorio Alfieri
