tmux nested

hi:
I am trying to use tmux nested. I use tmux background to open a docker, then in this docker, I use tmux again, the following is my problems:
If I use docker run -it *, tmux can work well. But when I use docker exec -it *, tmux is no respoding:

Is there any idea?
Thanks a lot!

[nicm]

This issue does not include enough information. Please read the CONTRIBUTING file.

hi:
I use tmux 1.8 in ubuntu14.04 as the server, which run many dockers on it. The following is the info of server:

and I start a docker with ubuntu16.04, tmux 2.1, the following is the info:

The problom is when I use docker exec -it * /bin/bash, in the terminal, the command tmux has no response:

Is there any idea?
Thanks~

[nicm]

What's in the tmux logs from the one that doesn't work? What does running tmux with "strace -f -ostrace.out tmux ..." show in strace.out?

…

On Fri, 18 May 2018, 09:19 Wei Wang, ***@***.***> wrote: hi: I use tmux 1.8 in ubuntu14.04 as the server, which run many dockers on it. The following is the info of server: [image: 2018-05-18 16 16 30] <https://user-images.githubusercontent.com/35212977/40223816-de1f7c4e-5ab6-11e8-80d0-939debf81307.png> and I start a docker with ubuntu16.04, tmux 2.1, the following is the info: [image: 2018-05-18 16 17 16] <https://user-images.githubusercontent.com/35212977/40223854-f63385be-5ab6-11e8-8395-9cdd8b2d8583.png> The problom is when I use docker exec -it * /bin/bash, in the terminal, the command tmux has no response: [image: 2018-05-18 16 18 47] <https://user-images.githubusercontent.com/35212977/40223923-3085d69a-5ab7-11e8-9f61-4f0d0126ad51.png> Is there any idea? Thanks~ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1347 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASkc4EBj9xrr9oJF39LjFew4g3QXN9nks5tzoQRgaJpZM4UERWs> .

Thanks for your reply.
Yes, the tmux in docker dose not work.
BTY, the following shows the tmux-server-128.log after run $tmux -vv -Ltest -f/dev/null new

and the tmux-clinet-126.log is empty.

[nicm]

Does this still happen with tmux 2.7?

…

On Fri, 18 May 2018, 09:29 Wei Wang, ***@***.***> wrote: Thanks for your reply. Yes, the tmux in docker dose not work. BTY, the following shows the tmux-server-128.log after run $tmux -vv -Ltest -f/dev/null new [image: 2018-05-18 16 26 23] <https://user-images.githubusercontent.com/35212977/40224302-53f1a194-5ab8-11e8-9304-b5e67648c108.png> and the tmux-clinet-126.log is empty. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1347 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASkc2DA0W7GnL4_3C4cZYzM9OfJnEDoks5tzoZZgaJpZM4UERWs> .

Thanks a lot. It works well when I change tmux in server from v1.8 to v2.1.
BYW, I wonder is there any idea to get an new panel in docker.
Currently, when I use control-b + c with tmux in docker:

It will create a new session parallel with the docker session:

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.