[lxc-users] undefined symbol: current_config on custom-compiled lxc2

[Tycho Andersen]

On Mon, Jul 18, 2016 at 04:17:48PM +0300, Nikolay Borisov wrote:
> Hello List,
> 
> 
> So I tried compiling boh lxc 2.0 from github as well as the 2.0.3 stable
> package from the web page. Everything went fine:
> 
> ----------------------------
> Environment:
>  - compiler: gcc
>  - distribution: centos
>  - init script type(s): sysvinit
>  - rpath: no
>  - GnuTLS: no
>  - Bash integration: yes
> 
> Security features:
>  - Apparmor: no
>  - Linux capabilities: yes
>  - seccomp: yes
>  - SELinux: yes
>  - cgmanager: no
> 
> Bindings:
>  - lua: yes
>  - python3: yes
> 
> Documentation:
>  - examples: yes
>  - API documentation: yes
>  - user documentation: yes
> 
> Debugging:
>  - tests: no
>  - mutex debugging: no
> 
> Paths:
>  - Logs in configpath: no
> 
> 
> However, when I try running lxc-create or lxc-start I get the following
> error: lxc-start: symbol lookup error: lxc-start: undefined symbol:
> current_config. Ldd on the lxc-ls binary shows that all libraries are
> resolved. This is on centos 6.7 box with 4.4 kernel. Any ideas?

What is the actual output of ldd? I suspect you're picking up the
system's liblxc with your custom compiled lxc binaries, which if the
system's liblxc is old enough will cause problems.

ldconfig -v may shed some light.

Tycho