Skip to content
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

[AIRSONIC] Won't install. #590

Closed
indivisionjoe opened this issue Jun 24, 2021 · 7 comments · Fixed by #592
Closed

[AIRSONIC] Won't install. #590

indivisionjoe opened this issue Jun 24, 2021 · 7 comments · Fixed by #592
Labels
bug Something isn't working

Comments

@indivisionjoe
Copy link

Describe the bug
App never leaves the deploying state.

To Reproduce
I changed:

  1. Path to /config
  2. Added path to /music folder
  3. runAsGroup ID to something friendly

No other changes from defaults.

Expected behavior
App would install.

Additional context
I'm not able to get any logs for the app to add.

@indivisionjoe indivisionjoe added the bug Something isn't working label Jun 24, 2021
@stavros-k stavros-k mentioned this issue Jun 25, 2021
11 tasks
@stavros-k
Copy link
Member

While there is a missing property making it unable to deploy, changing runAsUser/runAsGroup is not guaranteed that any app will play well!

@Ornias1993
Copy link
Member

Yeah, not every container is compatible with k8s security settings (such as runAsGroup and runAsUser), for example: linuxserver.io containers are not.
It's not really something we can fix from out end...

The missing properties and such, however, are something we should fix :)

@indivisionjoe
Copy link
Author

Ok. Good to know. To be clear, I only change the group setting if/when it's offered as a field. I'm not manually adding that or anything.

@Ornias1993
Copy link
Member

Ok. Good to know. To be clear, I only change the group setting if/when it's offered as a field. I'm not manually adding that or anything.

We just offer it because some advanced helm users might want to play with it.

Just because something is available does NOT mean we ensure changing it doesn't break anything, we offer a LOT of options that we would advice against using ourselves.

@indivisionjoe
Copy link
Author

Maybe we are referring to two different things. If you can't affect which user or group the app runs as (a routine solution many people used in the jail system) what is the alternative for sharing permissions for the same files between different ways of accessing them?

@Ornias1993
Copy link
Member

If you can't affect which user or group the app runs as (a routine solution many people used in the jail system) what is the alternative for sharing permissions for the same files between different ways of accessing them?

The alternative would not be our problem to supply.
We supply both the option to use env-based (linuxsserver.io) and native k8s-based permissions/runAsUser options.
If said container does not supply any of those options, that is an issue for the original creator of the container, not for truecharts.

Please remember: We only supply Helm Charts and SCALE GUI elements.
We do (most often) not supply anything directly related to the App itself.

@truecharts-admin
Copy link
Collaborator

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists

@truecharts truecharts locked and limited conversation to collaborators Feb 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants