Add vagrant environment #1
Conversation
|
A few comments, I ll try to run it on my localhost but otherwise looks good. |
|
|
||
| mbbox.vm.provider :libvirt do |domain| | ||
| # Season to taste | ||
| domain.cpus = 6 |
cverna
Feb 25, 2020
Member
I think we need to use something like in bodhi (https://github.com/fedora-infra/bodhi/blob/develop/Vagrantfile#L103, https://github.com/fedora-infra/bodhi/blob/develop/Vagrantfile#L21) so that it is using the maximum number of cpus the host can provide.
I think we need to use something like in bodhi (https://github.com/fedora-infra/bodhi/blob/develop/Vagrantfile#L103, https://github.com/fedora-infra/bodhi/blob/develop/Vagrantfile#L21) so that it is using the maximum number of cpus the host can provide.
Zlopez
Feb 25, 2020
Author
Contributor
This looks much better, I will update it.
This looks much better, I will update it.
| VAGRANTFILE_API_VERSION = "2" | ||
|
|
||
| Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| | ||
| config.vm.box = "fedora/30-cloud-base" |
cverna
Feb 25, 2020
Member
Should we use Fedora 31 ?
Should we use Fedora 31 ?
cverna
Feb 25, 2020
Member
Ha that will be an issue with docker :(
Ha that will be an issue with docker :(
Zlopez
Feb 25, 2020
Author
Contributor
I tried it at first, but the cgroups v2 are not compatible with docker.
I tried it at first, but the cgroups v2 are not compatible with docker.
| @@ -20,10 +20,10 @@ spec: | |||
| dockerfile: |- | |||
| # Apache on centos7 keeps throwing segfaults... | |||
| #FROM centos:7 | |||
| FROM fedora:latest | |||
| FROM fedora:30 | |||
cverna
Feb 25, 2020
Member
Let's use Fedora 31
Let's use Fedora 31
Zlopez
Feb 25, 2020
Author
Contributor
This didn't worked on F31, this is why I changed latest to F30
This didn't worked on F31, this is why I changed latest to F30
Zlopez
Feb 25, 2020
Author
Contributor
But I don't remember, why it didn't worked
But I don't remember, why it didn't worked
Zlopez
Feb 25, 2020
Author
Contributor
I remember now, it was the fix that is in the dockerfile, this file didn't existed on F31
I remember now, it was the fix that is in the dockerfile, this file didn't existed on F31
cverna
Feb 25, 2020
Member
I think this is because in F31 instead of python2.7 it will be python3.7 in the path.
I think this is because in F31 instead of python2.7 it will be python3.7 in the path.
| @@ -23,7 +23,7 @@ spec: | |||
| FROM fedora:latest | |||
cverna
Feb 25, 2020
Member
Let's pin to Fedora 31
Let's pin to Fedora 31
Zlopez
Feb 25, 2020
Author
Contributor
Ok
Ok
|
I did the changes |
Zlopez
moved this from In progress
to Review in progress
in CentOS Stream update (Sustaining Team)
Vagrant environment sets up OpenShift environment for development. The liveliness and readiness probe for koji is still not working. This causes error to be thrown at the end of the mbbox script. Koji still needs some work, but this environment should be enough to start working with this script locally. Signed-off-by: Michal Konečný <mkonecny@redhat.com>
Vagrant environment sets up OpenShift environment for development.
The liveliness and readiness probe for koji is still not working.
This causes error to be thrown at the end of the mbbox script.
Koji still needs some work, but this environment should be enough to
start working with this script locally.
Signed-off-by: Michal Konečný mkonecny@redhat.com