ephemeral-port-reserve
Sometimes you need a networked program to bind to a port that can't be hard-coded. Generally this is when you want to run several of them in parallel; if they all bind to port 8080, only one of them can succeed.
The usual solution is the "port 0 trick". If you bind to port 0, your kernel will find some arbitrary high-numbered port that's unused and bind to that. Afterward you can query the actual port that was bound to if you need to use the port number elsewhere. However, there are cases where the port 0 trick won't work. For example, mysqld takes port 0 to mean "the port configured in my.cnf". Docker can bind your containers to port 0, but uses its own implementation to find a free port which races and fails in the face of parallelism.
ephemeral-port-reserve provides an implementation of the port 0 trick which
is reliable and race-free. You can use it like so:
PORT="$(ephemeral-port-reserve)"
docker run -p 127.0.0.1:$PORT:5000 registry:2
ephemeral-port-reserve is a utility to bind to an ephemeral port, force it into
the TIME_WAIT state, and unbind it.
This means that further ephemeral port alloctions won't pick this "reserved" port,
but subprocesses can still bind to it explicitly, given that they use SO_REUSEADDR.
By default on linux you have a grace period of 60 seconds to reuse this port.
To check your own particular value:
$ cat /proc/sys/net/ipv4/tcp_fin_timeout
60
NOTE: By default, the port returned is specifically for localhost, aka 127.0.0.1.
If you bind instead to 0.0.0.0, you may encounter a port conflict. If you need to
bind to a non-localhost IP, you can pass it as the first argument.
Metadata
Release files for ephemeral-port-reserve 1.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ephemeral_port_reserve-1.1.4.tar.gz | 3.5 kB | Without provenance | Details for ephemeral_port_reserve-1.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ephemeral_port_reserve-1.1.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for ephemeral_port_reserve-1.1.4-py2.py3-none-any.whl |
Total release size: 8.0 kB
Release files / ephemeral_port_reserve-1.1.4.tar.gz
| Download URL | ephemeral_port_reserve-1.1.4.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8f7da2c97090cb0801949dec1d6d40c97220505b742a70935ffbd43234c14b2
|
|
BLAKE2b-256 checksum How to use checksums |
ef933f0b75f75f94227f67ccfe86f989415e40ac054dd67b55dfac7abdc0a2d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.5.0.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.5.2
|
Release files / ephemeral_port_reserve-1.1.4-py2.py3-none-any.whl
| Download URL | ephemeral_port_reserve-1.1.4-py2.py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
dae8da99422c643bb52478ed55d5a8428099092391656ba3726ff30c801600c8
|
|
BLAKE2b-256 checksum How to use checksums |
2d2f28948390896745afd561dad6a39daf49f74637b7b3398582a649b5acc4c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.5.0.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.5.2
|
Security for ephemeral-port-reserve 1.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.