Subutai attach to container does not work

subutai-io / agent

Subutai Agent is a tool that provides CLI to control Subutai infrastructure, and is a daemon that receives and performs Management commands through secured channels

https://subutai.io

15 stars 15 forks source link

Subutai attach to container does not work #997

Open absidish opened 5 years ago

absidish commented 5 years ago

Checked on 3 peers: 2 master peers and 1 dev peer have the same issue version :

8.8.0+201904110910160

root@subutai:/# subutai list i
NAME            STATE    IP        Interface
----            -----    --        ---------
Container1-8dm-1-3    RUNNING    172.23.85.3    eth0
Container2-ac7-1-4    RUNNING    172.23.85.4    eth0
management        RUNNING    10.10.10.1    eth0
root@subutai:/# subutai attach Container1-8dm-1-3
subutai: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
root@subutai:/# subutai update rh -c 
INFO[2019-04-12 06:23:43] No update is available                       
root@subutai:/# subutai -v
8.8.0+201904110910160
root@subutai:/#

master-peer-eu-1:~# subutai attach Container1-xxw-1-3
subutai: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
master-peer-eu-1:~#

dilshat commented 5 years ago

@absidish Please try to update the peers, restart and check again Probably related to this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911090

absidish commented 5 years ago

Updated RH, restarted, bug is still here

root@subutai:/home/subutai# subutai attach  Container2-ac7-1-4
subutai: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
root@subutai:/home/subutai# subutai update rh -c
INFO[2019-04-15 06:02:09] No update is available                       
root@subutai:/home/subutai# subutai -v 
8.8.0+201904110910160
root@subutai:/home/subutai#

absidish commented 5 years ago

created RH with vagrant

vagrant init --minimal subutai/stretch; SUBUTAI_CPU=2 SUBUTAI_RAM=4096  SUBUTAI_ENV=dev SUBUTAI_DISK=300  vagrant up

kurmanbekova6 commented 5 years ago

Containers were successfully attached on different master peers Tested with the same configuration as @absidish 's. Screenshot_13 Screenshot_14

akarasulu commented 5 years ago

Was this bug fixed @absidish @kurmanbekova6 @Dilshat ?

dilshat commented 5 years ago

That was a specific peer's problem. Has not been reproduced

absidish commented 5 years ago

I could reproduce, need to reinstall host machine to check exactly, I'll back soon with test results

niclash commented 5 years ago

I also came across this today. On my peer there are multiple containers, and only one container have this behavior. The significant difference of that non-working container is that it is running Buster template inside, rather than Stretch template.