should be addressed in OKD 4.0 so I am really looking forward to trying it out
and will make my life as an ops easier. So thank you again so much for the
effort.
Best regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Thursday, June 20, 2019 11:19 PM, Clayton Coleman
wrote:
> TL:DR - I can’t e
> Dale Bewley
>
> > On Feb 11, 2019, at 04:31, mabi m...@protonmail.ch wrote:
> > Hello,
> > I installed okd 3.12 using the Ansible playbook deploy_cluster.yml and now
> > I was having the following questions regarding configuration changes to the
> > cluste
having deployed with Ansible?
Regards,
Mabi
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
docker.yml#L174
>
> --
> Mateus Caruccio / Master of Puppets
> GetupCloud.com
> We make the infrastructure invisible
> Gartner Cool Vendor 2017
>
> Em sex, 25 de jan de 2019 às 16:48, mabi escreveu:
>
>> There are no symlinks and /var/lib/docker still exists. Looking at the
; /var/lib/containers/docker.
>
> --
> Mateus Caruccio / Master of Puppets
> GetupCloud.com
> We make the infrastructure invisible
> Gartner Cool Vendor 2017
>
> Em sex, 25 de jan de 2019 às 11:43, mabi escreveu:
>
>> I changed the /etc/sysconfig/docker-storage-setup
48125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar:
no space left on device\" "], "stdout": "", "stdout_lines": []}
‐‐‐ Original Message ‐‐‐
On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio
wrote:
> oops, didn
ub.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47
>
> --
> Mateus Caruccio / Master of Puppets
> GetupCloud.com
> We make the infrastructure invisible
> Gartner Cool Vendor 2017
>
> Em qui, 24 de jan de 2019 às 15:52, mabi escrev
2 driver I followed the
following guide:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#using_the_overlay_graph_driver
Thanks for any hints.
Reg
I would be
using Atomic Host?
>>> On Sun, 6 Jan 2019 at 07:03, mabi wrote:
>>>
>>>> ‐‐‐ Original Message ‐‐‐
>>>> On Saturday, January 5, 2019 3:57 PM, Daniel Comnea
>>>> wrote:
>>>>
>>>>> [DC]:
d
as everything runs inside Docker containers.
Now I first have to figure out how to install my CentOS Atomic Host virtual
machines automatically with PXE and kickstart. It looks like I just need to
adapt my kickstart file for Atomic Host (rpm ostree) and I get Atomic Host
instead of plain
‐‐‐ Original Message ‐‐‐
On Saturday, January 5, 2019 3:57 PM, Daniel Comnea
wrote:
> [DC]: i think you are a bit confused: there are 2 ways to get the rpms from
> CentOS yum repo: using the generic repo [1] which will always have the latest
> origin release OR [2] where i've
‐‐‐ Original Message ‐‐‐
On Saturday, January 5, 2019 10:57 AM, Daniel Comnea
wrote:
> The specific openshift release directory been present for a long time.
> Saying that i'll work next week in pushing v3.11 rpms to
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ too
‐‐‐ Original Message ‐‐‐
On Friday, January 4, 2019 11:15 PM, Erik McCormick
wrote:
> Change it to use:
> http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
I see, so now there is one directory per version released and not all versions
in the same openshift-origin
-openshift-origin]
name=CentOS OpenShift Origin
baseurl=http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
Regards,
Mabi
___
users mailing list
users
Anyone?
‐‐‐ Original Message ‐‐‐
On Tuesday, December 18, 2018 11:19 AM, mabi wrote:
> Hello,
>
> My v3.10 OpenShift OKD cluster is currently running version
> v3.10.0+7af7b71-75 and I wanted to upgrade to the latest v3.10 version which
> based on the git log of the op
Hello,
My v3.10 OpenShift OKD cluster is currently running version v3.10.0+7af7b71-75
and I wanted to upgrade to the latest v3.10 version which based on the git log
of the openshift-ansible repo should be -89.
For that purpose I have ran the following playbook from the release-3.10 branch
on
Hello,
I am running a small OKD 3.10 cluster on CentOS 7.6 and just noticed that the
controller-manager on my master node does not seem to start properly as you can
see from the "oc get pods" output below:
NAMESPACE NAME
READY
17 matches
Mail list logo