FS#78506 - [docker] Not all ipv6 port forwardings are created

Attached to Project: Community Packages
Opened by DeLord (DeLord) - Saturday, 13 May 2023, 14:12 GMT
Last edited by Toolybird (Toolybird) - Saturday, 03 June 2023, 23:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

ip6tables rules are not created correctly when a Docker container publishes ports, and is configured to use ip6tables to also to NAT for ipv6.

I created a bug report on upstream moby project regarding this, because I first thought it probably is an upstream bug. Please read this bug report for the detailed bug description: https://github.com/moby/moby/issues/45459

After a couple of additional days, I rather think the chance is higher that it might be an error somewhere in the Arch Linux packages, mainly because I couldn't reproduce the issue on other distros using - as far as I see - the same versions of relevant software. And also I hope I can find faster help here. :-)

Would be very nice to track this down together.

Additional info:
* package version(s): Docker 2.17.3-1
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 03 June 2023, 23:50 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream ticket mentions it also happens on Gentoo. Not an Arch packaging bug apparently. Please follow up with upstream.
Comment by Toolybird (Toolybird) - Saturday, 13 May 2023, 22:35 GMT
This looks like a case of "I can't get it working so I'll just file a bug". Ugh, that's not how it works here. You'll need to first put some effort in to debug this yourself...especially as this is apparently some experimental feature.

> package version(s): Docker 2.17.3-1

Do you mean "docker-compose"?
Comment by DeLord (DeLord) - Sunday, 14 May 2023, 00:28 GMT
How do I deserve such a disrespectful and obviously too hasty written comment? Very disappointing and demotivating. I'm a Arch Linux power user since over 10 years, and never have I read such a bullshit.

What's even worse: Your argumentation doesn't even make sense. The same configuration on other Linux distributions result in the correct expected behavior. Talking about "I can't get it working" on Arch Linux is just wrong here. It works on other distros, it doesn't work under Arch. How's it me being stupid?

However, you're right. I copy-pastad the docker-compose version. Docker is at 1:23.0.5-2. You could have also already seen that when actually taking a look at and trying to understand the original upstream bug report.
Comment by Toolybird (Toolybird) - Sunday, 14 May 2023, 00:48 GMT
Yeah, righto chief. My response might not have been the greatest, but yours breaks the code of conduct [1]. Good luck.

[1] https://terms.archlinux.org/docs/code-of-conduct/#respect
Comment by DeLord (DeLord) - Sunday, 14 May 2023, 01:03 GMT
I don't understand. I'm just trying to make all our experience with Arch Linux better. A bug like this keeps people from actually enjoying Arch Linux. I'm trying to contribute, so that we don't have such kind of bugs.

Your first comment sounds like you are not taking my seriously. I was offended and wrote my answer.

"Good luck" sounds again like you don't care about this bug. Don't care about if people enjoy Arch Linux or not. I can't even express how bad I feel about this. This will be eventually the end of Arch Linux.
Comment by DeLord (DeLord) - Sunday, 14 May 2023, 01:30 GMT
PS: Maybe I over exaggerated with the "end of Arch Linux" sentence. Sorry for that. I'm a little triggered about this, and I know this is not productive.

If you're available, please contact me on Libera. Same nickname as here. I feel we should have a short chat about this, to clear things up. Thanks.

Loading...