Unexpected 401 error after getting Portus information

[leandrorusso]

Description

While using Portus, if you will execute into Portus frontend container the command below: "docker exec -it portusctl exec rake portus:info"

The current users logged will be redirected to the login page. Portus container logs show: Processing by TeamsController#index as HTML Completed 401 Unauthorized in 6ms (ActiveRecord: 0.9ms)

Portus version:2.5.0

[stale[bot]]

Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Jean-Baptiste-Lasselle]

HI @leandrorusso , If there is anything (I mean, any, thing), you would like to do with rake inside portus container, you can also do it using Portus API and curl. Or portusctl, but I don't recommend portusctl, because :

• portusctl is badly coded in golang
• portusctl is absolutely not maintained
• and portusctl does nothing that curl does not do a 10^32 (around the Avogadro number) times better.
  • and we rar ein the cloud, we use REST API, SystemD or SystemV is a Jurassic debate :)

see https://github.com/SUSE/Portus/issues/2244#issuecomment-585557198