Public bug reported:

Using LXD v2.20 on Ubuntu 16.04 host, with kernel
Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

I get the following

# cat /proc/sys/net/ipv4/tcp_keepalive_time
cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory

I'm informed from linuxcontainers.org, that this is a kernel bug.
https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891

I happen to be trying to run Kolab.org in a container, and some of their python 
code errors as this is parameter is not found. Clearly someone has found this 
in Kolab before as there's a patch
https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch
But the problem is in other places too.

It could be argued that Kolab should code round this issue.
But on the other hand, with out it, and in general, other applications would 
not run in containers, which perhaps is a undesirable limitation.

Thus it's why I'm reporting here.
And there may be other parameters not appearing in the container too.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: lxd

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736804

Title:
  No tcp_keepalive_time in LXD container

Status in linux package in Ubuntu:
  New

Bug description:
  Using LXD v2.20 on Ubuntu 16.04 host, with kernel
  Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  I get the following

  # cat /proc/sys/net/ipv4/tcp_keepalive_time
  cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory

  I'm informed from linuxcontainers.org, that this is a kernel bug.
  
https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891

  I happen to be trying to run Kolab.org in a container, and some of their 
python code errors as this is parameter is not found. Clearly someone has found 
this in Kolab before as there's a patch
  
https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch
  But the problem is in other places too.

  It could be argued that Kolab should code round this issue.
  But on the other hand, with out it, and in general, other applications would 
not run in containers, which perhaps is a undesirable limitation.

  Thus it's why I'm reporting here.
  And there may be other parameters not appearing in the container too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736804/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to