Don't create a pty to run vtysh inside of the docker container #1792
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
Previously, when user run vtysh from the base system and disconnected from the terminal, the pty where vtysh was running in the container was left used. It is because of SIGHUP which is not passed inside of the docker. See moby/moby#28872 This patch don't create new pty to run vtysh in the container.
- How I did it
I changed command line option for docker exec.
- How to verify it
Build DUT and check
Or change /usr/bin/vtysh on DUT, run vtysh, disconnect from the terminal, connect back and check vtysh in the list of processes.
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)