Update: the listening ports are created if you specify a specific
address
root@neo4j-nmap:~# netstat -ant|grep LISTEN
tcp0 0 0.0.0.0:53550.0.0.0:* LISTEN
tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN
tcp0 0
>From my current experience on Ubuntu 16.10 and LXC managed by Proxmox
with Neo4j:
+ The service starts but does not create listening sockets after the
initial run, when the /etc/neo4j/neo4j.conf configuration is changed to
the following below:
neo4j.conf >> ++ dbms.connectors.default_listen_addr
Serge, thanks for looking. Here's the *release info. The lxc package
info is in description.
ubuntu@psyduck-maas20:~$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
ID=ubuntu
Ah, I'm sorry, I'd misread your info.
Your container is being started just fine, and has its own devices
cgroup.
What's actually happening is that the container is not allowed to
*reset* its devices cgroup. That is because lxc has set some device
cgroup limits, and the kernel is rightly forbiddi
I'm going to mark this invalid as I believe it's a non-issue. We may
want lxc and systemd to cooperate more to maximize the protection of
containerized services, though.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
On plain xenial, containers which I start as root get:
sudo lxc-info -H -p -n u1
18144
ubuntu@privlxc:~$ cat /proc/18144/cgroup
11:perf_event:/lxc/u1
10:devices:/lxc/u1/init.scope
9:hugetlb:/lxc/u1
8:memory:/lxc/u1
7:blkio:/lxc/u1
6:net_cls,net_prio:/lxc/u1
5:freezer:/lxc/u1
4:cpu,cpuacct:/lxc/u1
Thanks for reporting this bug.
Could you please show the precise Ubuntu release and lxc version?
cat /etc/*-release
dpkg -l | grep lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582364
Title:
