-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default transmission configuration is damaged #16
Comments
What is also interesting is that for a split second, it actually is correct. If I spam
|
Hi @ericgoedtel , Sorry, my bad. |
Haha okay thanks. I'm glad you knew about it. I was going bananas trying to figure out why it was happening to only me.😆 |
The transmission config file is being overwritten everytime the pod restarts :-( |
Was checking this project out for the first time. Forgive me for my k8s/k3s laypersonship.
Ran the x86 install, was unable to access Transmission. Ingress said 502 Bad Gateway. Checking out the logs indicated that the settings.json was malformed. Inspection of the JSON shows:
Obviously, something has been interpreted weird. So I scaled the replicaset to 0, nuked the file, and scaled back up:
That restored it back to the application default which has the tragic side-effect of turning whitelisting back on. Back to the drawing board. Lets try a new deployment:
Isolated the issue to the deployment args by manually replacing the JSON being echo'd into the config file:
Success. The config file literally just says "deadbeef." So there seems to be something wrong with the way the JSON is being spit out into the config file as a deployment argument.
Running on a bare-metal Ubuntu 20.04 server, if that matters.
The text was updated successfully, but these errors were encountered: