exec_resize method will be create two tcp connect please help me see see
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
my code
def set_exec_resize(self,exec_id,height,width):
try:
self.docker_client.exec_resize(exec_id,height,width)
except Exception as e:
return ("[+] ERROR %s" % e)
print "[-]set exec_resize:", commands.getoutput("netstat -anlp|grep 10.100.49.64")
return True
def start_exec(self, exec_id):
sock = self.docker_client.exec_start(exec_id, tty=True, socket=True)
print "[-]start exec :", commands.getoutput("netstat -anlp|grep 10.100.49.64")
return sock
self.ssh = f.start_exec(exec_id=exec_id)
f.set_exec_resize(exec_id=exec_id, height=height, width=width)
this will be create two tcp connect; and I can not close the exec_resize method create tcp connect ;that will be Leaked connection ;
I use tls connect will have the problem;not tls no problem;

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Python client's exec_start and exec_resize entry points shown in the report, then compare their TCP behavior with and without TLS. Verify how the resize request's connection is managed and reproduce the two-connection case; done means exec_resize no longer leaves a leaked connection, with coverage for the TLS case if the repository has relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100