-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'podman exec' resets the terminal size to 80x24 #3946
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
this is a dup of #3903 |
debarshiray
pushed a commit
to tagoh/toolbox
that referenced
this issue
Sep 5, 2019
See: containers/podman#3946 COLUMNS and LINES may not be set in the user's environment. Hence the existing mechanism for preserving environment variables don't work. https://github.com/debarshiray/toolbox/issues/242
debarshiray
pushed a commit
to tagoh/toolbox
that referenced
this issue
Sep 9, 2019
See: containers/podman#3946 COLUMNS and LINES may not be set in the user's environment. Hence the existing mechanism for preserving environment variables don't work. Note that for things to keep working when invoked via D-Bus from inside a toolbox container, the terminal size needs to be queried using the standard input stream, instead of explicitly mentioning the controlling terminal device /dev/tty. This is because stty(1) doesn't have the notion of a controlling terminal when invoked via D-Bus, but flatpak-spawn(1) ensures that the standard input stream still points to the user's interactive terminal. https://github.com/debarshiray/toolbox/issues/242
debarshiray
added a commit
to containers/toolbox
that referenced
this issue
Sep 9, 2019
When running nested, stty(1) is invoked against the inner pseudo-terminal pair created by 'podman exec --tty' which may not have a valid size due to: containers/podman#3946 In such cases, the COLUMNS and LINES variables set by toolbox(1) in the outer environment should be forwarded. This should have been part of commit 05544fb. https://github.com/debarshiray/toolbox/issues/242
This was referenced Sep 9, 2019
debarshiray
added a commit
to containers/toolbox
that referenced
this issue
Sep 10, 2019
When running nested, stty(1) is invoked against the inner pseudo-terminal pair created by 'podman exec --tty' which may not have a valid size due to: containers/podman#3946 In such cases, the COLUMNS and LINES variables set by toolbox(1) in the outer environment should be forwarded. This should have been part of commit 05544fb. https://github.com/debarshiray/toolbox/issues/242
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
Somewhere between
podman-1.4.4-4.fc29
andpodman-1.5.1-3.fc29
,podman exec
started to reset the inner terminal's size to 80x24 even if the outer terminal had different dimensions.Reverting
runc
doesn't help. eg., I went as far back asrunc-1.0.0-57.dev.git9e5aa74.fc29
.In order to reproduce, resize the window of your terminal emulation application, and then use
less(1)
to render some text. You will see thatless(1)
either doesn't use the full extent of the terminal or uses too much, depending on whether your terminal emulation window is bigger or smaller than 80x24.This doesn't affect terminals created by
podman run
.This isn't affected:
However, this is affected:
Additional information you deem important (e.g. issue happens only occasionally):
Reproducible at will.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: