[Unraid OS version 6.9.0-beta35 available]

You're completely missing the point. We're glad that you integrated it. We're unhappy that our efforts and calls for help were largely ignored over the years. You never even reached out to the folks who maintained it for years. Then you have the gall to say you did it to discourage "unofficial" builds as if it was a bad thing that they provided it for years.

 

Yeah, I'm out, too. Not a fan of a one way street.

 

 

[Unraid OS version 6.9.0-beta35 available]

24 minutes ago, limetech said:

Not a slap at all, instead it's acknowledgment of their efforts.

?? I don't see any acknowledgement

[Unraid OS version 6.9.0-beta35 available]

1 hour ago, limetech said:

Finally, we want to discourage "unofficial" builds of the bz* files.

Wow. Talk about a slap in the face. @CHBMB and @bass_rock busted their behinds for years to provide a working solution to unraid users with minimal input and no acknowledgement from limetech. They had to do so much trial and error trying to figure out what may or may not have changed in unraid (out of tree drivers and whatnot) with each new version.

 

All of a sudden limetech finally decides to roll out a solution and they want to 'discourage "unofficial" builds of the bz* files'.

Nice one.

[custom docker network does not allow entering container port in mapping]

Ah, gotcha. Will do

[custom docker network does not allow entering container port in mapping]

12 hours ago, ken-ji said:

Seems like the UI doesn't fully support the custom bridge network yet. (Haven't had a use case for it myself)

If you want your containers to be able to connect to each other using container names as hostnames, then the user defined bridge network works great. Letsencrypt takes advantage of this to standardize proxy configs by using container names instead of IPs

[custom docker network does not allow entering container port in mapping]

3 hours ago, bonienl said:

This is not supported in the GUI. You'll need to make a feature request.

I believe this is a bug.

 

The feature was already requested and it was added. The "user defined bridge" networks are already listed in the gui as a network option.

 

The bug is that when a user defined network is selected, the "add port" screen does not allow for entering in the "container port". See below screenshot.

 

[custom docker network does not allow entering container port in mapping]

Bump