Closed AuqW9cQ closed 2 weeks ago
Are you using the docker compose from the docs?
First of all, thanks for your responce.
Im running the Container in my kubernetes cluster, deployed via Flux.
Here´s my helmrelease.yml
---
# yaml-language-server: $schema=https://raw.githubusercontent.com/bjw-s/helm-charts/main/charts/other/app-template/schemas/helmrelease-helm-v2.schema.json
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: musicassistant
spec:
interval: 15m
chart:
spec:
chart: app-template
version: 3.4.0
sourceRef:
kind: HelmRepository
name: bjw-s-charts
namespace: flux-system
interval: 15m
install:
createNamespace: true
remediation:
retries: 5
upgrade:
remediation:
retries: 5
values:
controllers:
musicassistant:
pod:
securityContext:
runAsUser: 568
runAsGroup: 568
runAsNonRoot: true
fsGroup: 10081
fsGroupChangePolicy: OnRootMismatch
containers:
main:
image:
repository: ghcr.io/music-assistant/server
tag: 2.2.0
resources:
requests:
cpu: 47m
memory: 512Mi
limits:
memory: 1024Mi
probes:
liveness:
enabled: true
readiness:
enabled: true
env:
TZ: Europe/Berlin
service:
main:
controller: musicassistant
type: LoadBalancer
loadBalancerIP: 192.168.1.10 # set this Published IP Adress
annotations:
metallb.universe.tf/allow-shared-ip: "true"
ports:
http:
port: 8095
stream1:
port: 8097
targetPort: 8097
stream2:
port: 8098
targetPort: 8098
api:
port: 9000
protocol: TCP
sbcli:
port: 9090
protocol: TCP
psb:
port: 3483
protocol: TCP
second:
controller: musicassistant
type: LoadBalancer
loadBalancerIP: 192.168.1.10
annotations:
metallb.universe.tf/allow-shared-ip: "true"
ports:
psb-udp:
port: 3483
protocol: UDP
ingress:
main:
enabled: true
className: nginx
hosts:
- host: musicassistant.mydomain.local
paths:
- path: /
pathType: Prefix
service:
identifier: main
port: http
persistence:
config:
enabled: true
existingClaim: musicassistant-config
globalMounts:
- path: /data
music:
existingClaim: musicassistant-music-pvc
We cant support kubernetes setups. Have a look at our example docker configs (especially about the permissions).
Also, I'm not a Kubernetes expert but I notice multiple issues in your setup:
Basically, you are on your own for setup. We really do not have the manpower to support complex setups like this, sorry. Ofcourse if you find out how to make it work, feel free to share your experience to help others.
What version of Music Assistant has the issue?
2.2.7
What version of the Home Assistant Integration have you got installed?
2024.10.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
When i try to update MA from 2.2.0 to 2.2.7 i got the following log:
How to reproduce
Update Container from 2.2.0 to 2.2.7 with installed Slimproto
Music Providers
The Problem is during starting the container, so the problem is no result of playing music.
Installed are: MusicAssistant RadioBrowser Spotify Filesystem (Local disk)
Player Providers
Slimproto
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.10.2
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Alternative