When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen?
Thanks!
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
On 9/27/19 9:00 AM, Lance Albertson wrote:
When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen?
Thanks!
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
I published my initial CentOS 8 images for Docker, and Vagrant earlier this week. The Docker image could certainly be improved, but your welcome to use it:
https://hub.docker.com/r/roboxes/centos8
You can also find the Packer templates and scripts used to create it (and suggest improvements) here:
https://github.com/lavabit/roboxes/
On my own list of TODOs: the RHEL 8 and by extension, the CentOS 8 version of Anaconda, require a number of microcode/firmware packages that were typically removed from RHEL 7 and CentOS 7 containers. But they need to be included with 8, or it breaks the automated install process. I haven't tried removing them post-install yet.
I believe Brian Stinson, who has posted to this list in the past, has been building CentOS 8 containers for a couple of months, but I don't know if any of his images, or configs are available for download. You can always ask though.
L~
On Fri, Sep 27, 2019 at 8:12 AM Ladar Levison via CentOS-devel < centos-devel@centos.org> wrote:
On 9/27/19 9:00 AM, Lance Albertson wrote:
When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen?
Thanks!
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
I published my initial CentOS 8 images for Docker, and Vagrant earlier this week. The Docker image could certainly be improved, but your welcome to use it:
https://hub.docker.com/r/roboxes/centos8
You can also find the Packer templates and scripts used to create it (and suggest improvements) here:
Looks like the correct URL is https://github.com/lavabit/robox
On Thu, Sep 26, 2019, at 22:30, Lance Albertson wrote:
When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen?
Thanks!
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
-- Lance Albertson Director Oregon State University | Open Source Lab _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Here's what we're working through:
We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling.
Both cloud and container images are in the QA process and we'll get them out as soon as they're ready.
Cheers! -- Brian
On 9/27/19 6:29 AM, Brian Stinson wrote:
Here's what we're working through:
We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling.
Both cloud and container images are in the QA process and we'll get them out as soon as they're ready.
To expand a bit on this, the "old" tooling at https://github.com/CentOS/sig-cloud-instance-build produces a ~42MB tarball, and an imported container space of around 210MB.
The exact same kickstart used through pungi/koji to automate the container process produces a ~60MB tarball and a 360MB base container, because several additional packages are included for ...reasons.
I'm likely going to publish the container produced the *old* way while we debug the issues in the compose tooling.
On Fri, Sep 27, 2019 at 7:00 AM Jim Perrin jperrin@centos.org wrote:
On 9/27/19 6:29 AM, Brian Stinson wrote:
Here's what we're working through:
We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling.
Both cloud and container images are in the QA process and we'll get them out as soon as they're ready.
To expand a bit on this, the "old" tooling at https://github.com/CentOS/sig-cloud-instance-build produces a ~42MB tarball, and an imported container space of around 210MB.
The exact same kickstart used through pungi/koji to automate the container process produces a ~60MB tarball and a 360MB base container, because several additional packages are included for ...reasons.
I'm likely going to publish the container produced the *old* way while we debug the issues in the compose tooling.
Sounds good! Thanks for the quick update.
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
It seems the CentOS 8 images are released for only x86_64 architecture, thought it is announced on above issue page. :)
https://hub.docker.com/_/centos?tab=tags
``` $ uname -m x86_64
$ podman run --rm -t docker.io/centos:8 cat /etc/redhat-release CentOS Linux release 8.0.1905 (Core) ```
On 10/4/19 5:34 AM, Jun Aruga wrote:
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
It seems the CentOS 8 images are released for only x86_64 architecture, thought it is announced on above issue page. :)
Yeah, I need to work through the aarch64 and ppc64le containers with bstinson still. Hopefully we'll be able to get those done soon.
At least for the cloud images we have never been happy with the frequency and timing of the releases, eg 7.7 images are still not out. We used to take the raw image and generate cloud images for all the 3 public clouds but with 8.1 image builder finally supports GCP as well so you can just use that to build custom cloud images for AWS, GCP and Azure in a unified way.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm...
On Fri, Sep 27, 2019 at 9:30 AM Brian Stinson brian@bstinson.com wrote:
On Thu, Sep 26, 2019, at 22:30, Lance Albertson wrote:
When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen?
Thanks!
[1] https://github.com/CentOS/sig-cloud-instance-images/issues/151
-- Lance Albertson Director Oregon State University | Open Source Lab _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Here's what we're working through:
We have cloud and container images built, but we currently aren't happy with the base image size produced by our tooling.
Both cloud and container images are in the QA process and we'll get them out as soon as they're ready.
Cheers!
Brian _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, Dec 5, 2019 at 9:31 AM Akshay Kumar akshayk@gmail.com wrote:
At least for the cloud images we have never been happy with the frequency and timing of the releases, eg 7.7 images are still not out. We used to take the raw image and generate cloud images for all the 3 public clouds but with 8.1 image builder finally supports GCP as well so you can just use that to build custom cloud images for AWS, GCP and Azure in a unified way.
Since it is a matter of a few minutes work to install one, run an update, and store your personal imae *with* enhanced networking enabled, Isn't it enough to simply have a base older OS to work with? If necessary, you can even restrict your updates to not use the "updates" repositories and only update to the next release time base image. RHEL does not support this without a nightmare of grabbing a DVD image and mounting that somewhere to get the release time packages only, but CentOS releases have been very good about publishing the release time base operating system in clearn format.
On Thu, Dec 5, 2019, at 9:58 PM, Nico Kadel-Garcia wrote:
On Thu, Dec 5, 2019 at 9:31 AM Akshay Kumar akshayk@gmail.com wrote:
At least for the cloud images we have never been happy with the frequency and timing of the releases, eg 7.7 images are still not out. We used to take the raw image and generate cloud images for all the 3 public clouds but with 8.1 image builder finally supports GCP as well so you can just use that to build custom cloud images for AWS, GCP and Azure in a unified way.
Since it is a matter of a few minutes work to install one, run an update, and store your personal imae *with* enhanced networking enabled, Isn't it enough to simply have a base older OS to work with? If necessary, you can even restrict your updates to not use the "updates" repositories and only update to the next release time base image. RHEL does not support this without a nightmare of grabbing a DVD image and mounting that somewhere to get the release time packages only, but CentOS releases have been very good about publishing the release time base operating system in clearn format.
RHEL provides "kickstart" trees for each minor release, same as CentOS 8.
________________________________________ From: CentOS-devel centos-devel-bounces@centos.org on behalf of James Cassell fedoraproject@cyberpear.com Sent: December 5, 2019 10:03 PM To: CentOS Devel List Subject: Re: [CentOS-devel] CentOS 8 docker images
On Thu, Dec 5, 2019, at 9:58 PM, Nico Kadel-Garcia wrote:
On Thu, Dec 5, 2019 at 9:31 AM Akshay Kumar akshayk@gmail.com wrote:
At least for the cloud images we have never been happy with the frequency and timing of the releases, eg 7.7 images are still not out. We used to take the raw image and generate cloud images for all the 3 public clouds but with 8.1 image builder finally supports GCP as well so you can just use that to build custom cloud images for AWS, GCP and Azure in a unified way.
Since it is a matter of a few minutes work to install one, run an update, and store your personal imae *with* enhanced networking enabled, Isn't it enough to simply have a base older OS to work with? If necessary, you can even restrict your updates to not use the "updates" repositories and only update to the next release time base image. RHEL does not support this without a nightmare of grabbing a DVD image and mounting that somewhere to get the release time packages only, but CentOS releases have been very good about publishing the release time base operating system in clearn format.
RHEL provides "kickstart" trees for each minor release, same as CentOS 8.
And "kickstart"s are still way behind and broken.
_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Akshay Kumar -
Brian Stinson -
Dan Seguin -
James Cassell -
Jim Perrin -
John Broome -
Jun Aruga -
Ladar Levison -
Lance Albertson -
Nico Kadel-Garcia