On 29/06/18 19:13 +0200, Salvatore D'angelo wrote:
> Good to know. I'll try it. I'll try to work on VM too.
If that won't work, you can also try:
docker run ... --ulimit memlock=33554432 ...
where 32768 (kiB) may still be not enough (assuming the default
of 16384), hard to say, since proper
On Thu, Jun 21, 2018 at 10:47 AM Jason Gauthier wrote:
>
> On Thu, Jun 21, 2018 at 9:49 AM Jan Pokorný wrote:
> >
> > On 21/06/18 07:05 -0400, Jason Gauthier wrote:
> > > On Thu, Jun 21, 2018 at 5:11 AM Christine Caulfield
> > > wrote:
> > >> On 19/06/18 18:47, Jason Gauthier wrote:
> > >>>
Good to know. I'll try it. I'll try to work on VM too.
Il Ven 29 Giu 2018, 5:46 PM Jan Pokorný ha scritto:
> On 26/06/18 11:03 +0200, Salvatore D'angelo wrote:
> > Yes, sorry you’re right I could find it by myself.
> > However, I did the following:
> >
> > 1. Added the line you suggested to
On 29/06/18 10:00 +0100, Christine Caulfield wrote:
> On 27/06/18 08:35, Salvatore D'angelo wrote:
>> One thing that I do not understand is that I tried to compare corosync
>> 2.3.5 (the old version that worked fine) and 2.4.4 to understand
>> differences but I haven’t found anything related to
On 26/06/18 11:03 +0200, Salvatore D'angelo wrote:
> Yes, sorry you’re right I could find it by myself.
> However, I did the following:
>
> 1. Added the line you suggested to /etc/fstab
> 2. mount -o remount /dev/shm
> 3. Now I correctly see /dev/shm of 512M with df -h
> Filesystem Size
On 27/06/18 08:35, Salvatore D'angelo wrote:
> Hi,
>
> Thanks for reply and detailed explaination. I am not using the
> —network=host option.
> I have a docker image based on Ubuntu 14.04 where I only deploy this
> additional software:
>
> *RUN apt-get update && apt-get install -y wget git
