similar to: CentOS box images at Vagrant Cloud give 404

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

NOTE: This message was intended to go to centos-devel and centos-announce on 11-Feb-2021 but it only made it to centos-devel. Thanks to folks on IRC for mentioning that this never made it to the proper announcement channels. Hi folks, CentOS Stream container images are now readily available! podman pull quay.io/centos/centos:stream OR podman pull quay.io/centos/centos:stream8 ## Tags? We

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

Greetings Everyone Just playing around with the new version, And I'm having difficulties setting up Icecast to play with a second listening port on 80. If I turn off all of the websites, it works, BUT, if I have one on (3 IP addresses attached to the Nic...websites attached to port 192.168.0.90) it says it cannot create a listening port on port 80.

can someone overthere help? the server specs are as follows HP DL380G4 Dual Intel Xeon 3.2GHz processor with 4GB RAM, running fedora core 3 asterisk-1.2.5 ss7-0.8.3d. using sip as advised to receive calls from another gateway in US. using g729 in transcoding way. however, I noticed the call hit the 51 active calls which is 102channels, I run "top" to check the system resources usage

On 6/1/22 13:43, Fabian Arrotin wrote: > On 01/06/2022 19:51, Orion Poplawski wrote: >> Looks like the GPG key we use to sign our RPMs is not longer good with EL9: >> >> # rpm --import RPM-GPG-KEY-nwra >> error: RPM-GPG-KEY-nwra: key 1 import failed >> >> gpg key info: >> >> sec? rsa2048/35DDB0B86218AC2F >> ????? created: 2017-08-16?

This may provide the answer you are looking for: it's being deprecated in favor of Cockpit. https://bugzilla.redhat.com/show_bug.cgi?id=2030592 On Fri, Feb 10, 2023 at 6:58 AM G?nther J. Niederwimmer <gjn at gjn.priv.at> wrote: > hello list, > > I switched to version 9 (not redhat) on my "new" server, and that worked. > But > after updating to 9.1, the

On 03/26/2015 10:40 PM, Bob Hepple wrote: > Boris Epstein <borepstein at ...> writes: > a set of scripts/utilities for automatically >> starting and running headless (no X11) VM's using VirtualBox omn a CentOS 6 >> server. VNC/RDP access to the VM's would be fine. > vagrant? > > _______________________________________________ > I'm unfamiliar with

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository centos/centos.org. from 2459e4e Correct download links for ISO images for 7.7.1810 release new 0ce3254 Updating who/what/where/why for the world of two CentOS distros. - Quick blurb about each distro begins answering questions about the new distro - Release

Hi, In support of reproducible research at my Institute, I seek an approach to re-creating the R environments in which an analysis has been conducted. By which I mean, the exact version of R and the exact version of all packages used in a particular R session. I am seeking comments/criticism of this as a goal, and of the following outline of an approach: === When all the steps to an workflow

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7/x86_64 and for the first time for CentOS Linux 6/x86_64; We are providing box's for Livbirt provider and the Virtual Box provider. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available for the Libvirt and the VirtualBox providers in Vagrant. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available, as in the past, for the Libvirt and the VirtualBox providers in Vagrant. We have also enabled the vmware providers, for anyone using Vmware's products for backing Vagrant on Linux, MacOS or Windows. ref:

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would

I'm using libvirt on Debian/stretch (testing) with vagrant and the vagrant-libvirt plugin. When I import a vagrant box (jessie64.box), the resulting file permssions let anyone in the "kvm" group read the img. But when I build upon that box, only root can read it: -rw------- 1 root root 20198785024 Sep 19 18:19 buildserver_default.img -rwxr--r-- 1 libvirt-qemu kvm

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──