Closed ghost closed 1 year ago
As far as I can tell it only resets it to le
if you provide an invalid value.
lowcost
, throughput
, lowdelay
, all work fine and persist. Setting default
or foo
result in it being reset back to le
on startup.
Looks like any DSCP value is valid too.
In my case, it's been working as "default" since forever, and according to Transmission Docs values haven't changed.
Possible values are "default", "lowcost", "throughput", "lowdelay" and "reliability".
Could it be an undocumented change in Transmission release? Or is that value check performed by the container?
We're not changing anything in the config other than if you set the specific envs in the readme (user, pass, peerport, etc.), I suspect it's an undocumented change in v4.
Apparently yes, it's an undocumented change.
DSCP support was added initially in this commit and the latest change related to it listing the supported values for "peer-socket-tos" (DSCP and deprecated) can be found here, lines 351 to 390.
I guess you can close the issue, as is not container related. Thanks for the help.
Is there an existing issue for this?
Current Behavior
Every time you start the container, the "peer-socket-tos": value in the settings.json file gets replaced by "le", even if you change it with the container stopped.
Expected Behavior
It should honor the settings.json value or have a way to pass the env variable.
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
Container logs