#50140 lib389 containerised mode should use ipv4 and high ports
Closed: wontfix 5 years ago by firstyear. Opened 5 years ago by firstyear.

Issue Description

On docker ipv6 is not properly supported (and likely never will be). Additionally, linux blocks access to low ports by default.

Change --containerised installs to set higher port numbers, and to use ipv4 listeners only.


On docker ipv6 is not properly supported (and likely never will be).
Could you please elaborate on this a bit? What problem exactly are you facing?

Metadata Update from @vashirov:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

It's exactly what it means. Docker does not enable ipv6 by default, and probably never can because you need to provide a custom v6 prefix (there is no such thing as ipv6 nat).

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3199

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata