containers / containers/podman-compose
Port range syntax not supported
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 622
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
podman-compose refuses to start a service using port range syntax.
Related: containers/podman#15111
**To Reproduce**
Steps to reproduce the behavior:
1. use range syntax
2. `podman-compose up`
3. error message:
```
Error: host and container port ranges have different lengths: 11 vs 1
```
```yaml
name: bug
services:
busybox:
image: busybox:stable
ports:
- 127.0.0.1:6789-6799:8080
```
**Expected behavior**
Container starts, port inside the host range assigned
**Actual behavior**
podman-compose reports an error
**Output**
```
❯ podman-compose version
podman-compose version 1.5.0
podman version 5.8.0
❯ podman-compose up
Error: host and container port ranges have different lengths: 11 vs 1
[busybox] | Error: no container with name or ID "bug_busybox_1" found: no such container
```
**Environment:**
- OS: Linux
Contributor guide
Assessment
This issue has not been assessed yet.