**CentOS Virt SIG**
What:
- 'docker' (v1.9) http://cbs.centos.org/koji/buildinfo?buildID=10878
- 'docker-latest' (v1.10) http://cbs.centos.org/koji/buildinfo?buildID=10881
- both can be installed simultaneously and don't step on each other's toes,
but only one can run at a time.
- /usr/bin/docker is a script which execs /usr/bin/docker-current (v1.9) or
/usr/bin/docker-latest (v1.10) based on what $DOCKERBINARY is set to.
Why:
- some people want v1.9 (that includes kube and openshift iiuc)
- others want later versions
- people also want to switch between versions without having to
install/uninstall/reinstall
Comments?
--
Lokesh
Freenode: lsm5
GPG: 0xC7C3A0DD
I see there are new centos7 vagrant boxes dated 6/8 in http://cloud.centos.org/centos/7/vagrant/x86_64/images but they do not appear on the vagrant site at https://atlas.hashicorp.com/centos/boxes/7 yet.
Are there issues with the centos.org 1605_01 boxes, or alternately is there an expected date that the hashicorp site will catch up so 'vagrant box update' would get the new box ?
Also, any plans/dates/guesses for the centos6 boxes being made available ? I've kind of lost track of that plan in the other mailing list threads...
Thanks.
--
Vince Skahan
Infrastructure Engineering and Support
Office of Research Information Services (ORIS)
Hi,
The current version of Imagefactory [1] running with CentOS build system
(CBS) is few versions behind upstream releases of Imagefactory [1] .
Imagefactory recently added a new feature to build HyperV variant of
Vagrant image and also has capability to build Vagrant box for VMware
Fusion. I am confident that bringing these features to CBS will help the
community in general.
In case you are not aware about Imagefactory [1] , CBS uses it to do
Vagrant box builds for CentOS and other projects e.g. Atomic Developer
Bundle (ADB) in Atomic SIG.
I am wondering how we can facilitate a process to bring upstream
features of Imagefactory to CBS. One suggestion from Ian was that we
should create a cbs-test setup similar to production CBS setup and use
it to build confidence around the new features of Imagefactory and then
move the feature to production.
If you have better ideas you should speak now :)
[1] https://github.com/redhat-imaging/imagefactory
Thanks,
Lala
I'm not sure if this is an appropriate place for this question - please gently
steer me to a better place if you think there is one.
I have a machine using a kernel package from the CentOS Community Build System
(specifically kernel-3.18.21-16.el6 from
http://cbs.centos.org/koji/buildinfo?buildID=4757, but my question applies to
other CBS kernel versions as well from what I can tell)
The machine is crashing with some regularity on Sunday mornings. Looking at a
kdump core dump might help narrow down the cause of the crashes.
But the CBS kernel packages don't appear to include kernel-debuginfo packages,
and the kernel.spec file appears to me (a non-expert for sure) to have had the
necessary pieces removed, so I don't know how to rebuild from the srpm and get
the debuginfo packages that way either.
If someone could help me find or build the kernel-debuginfo package, it will be
appreciated.
Thank you,
RHSCL 2.2 was released recently [1] and this release includes several
new collections:
rh-mariadb101
rh-postgresql95
rh-maven33
rh-mongodb30upg
rh-mongodb32
rh-python35
rh-nodejs4
rh-ruby23
rh-ror42
SRPMs were taken and rebuilt for CentOS users in cbs.centos.org by SCLo
SIG group. The packages are now available in the testing repositories via:
sudo yum install centos-release-scl
sudo yum-config-manager --enable centos-sclo-rh-testing
sudo yum install rh-mariadb101
They will be soon moved to mirrors, but in case there are some issues,
let us know.
Please, mind, that these packages are not meant to be used on RHEL. On
RHEL you can acquire the packages as documented at [1].
[1]
https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/…
Regards,
Honza