automatic-ripping-machine: 🐋 CPU temp wont show correct number

Is there an existing issue for this?

• I have searched the existing issues

Does this issue exist in the latest version?

• I’m using the latest release

Describe the bug?

When running docker, CPU wont show correct temp

This may be hardware specific though.

To Reproduce

1. Install docker
2. Visit ui
3. No cpu temp

Built from source files ?

• I Built the image from source

What architecture are you seeing the problem on?

amd64

Expected behavior?

Show correct cpu temp

Relevant log output

Output from psutil.sensors_temperatures()

{
   "nvme":[
      "shwtemp(label=""Composite",
      current=33.85,
      high=74.85,
      critical=79.85)
   ],
   "nct6797":[
      "shwtemp(label=""SYSTIN",
      current=35.0,
      high=80.0,
      critical=80.0),
      "shwtemp(label=""PCH_CPU_TEMP",
      current=0.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""CPUTIN",
      current=32.0,
      high=115.0,
      critical=115.0),
      "shwtemp(label=""AUXTIN0",
      current=37.0,
      high=115.0,
      critical=115.0),
      "shwtemp(label=""AUXTIN1",
      current=-128.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""AUXTIN2",
      current=61.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""AUXTIN3",
      current=-3.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""SMBUSMASTER 0",
      current=50.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""PCH_CHIP_CPU_MAX_TEMP",
      current=0.0,
      "high=None",
      "critical=None)",
      "shwtemp(label=""PCH_CHIP_TEMP",
      current=0.0,
      "high=None",
      "critical=None)"
   ],
   "k10temp":[
      "shwtemp(label=""Tctl",
      current=49.625,
      "high=None",
      "critical=None)",
      "shwtemp(label=""Tccd1",
      current=37.75,
      "high=None",
      "critical=None)",
      "shwtemp(label=""Tccd2",
      current=47.0,
      "high=None",
      "critical=None)"
   ]
}

Anything else?

Tested and confirmed that the problem happens outside of docker

Code of Conduct

• I agree to follow this project’s Code of Conduct