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

Owntone 28.11 docker on Raspberry Pi 3 #13

Closed
stephane77777 opened this issue Feb 11, 2025 · 10 comments
Closed

Owntone 28.11 docker on Raspberry Pi 3 #13

stephane77777 opened this issue Feb 11, 2025 · 10 comments

Comments

@stephane77777
Copy link

Hi,
I have owntone 28.10 (linuxserver/daapd docker image arm64v8) and it works on my raspberry pi! I delete and recreate everything and it doesn't work.

mkdir -p $HOME/OwnTone/{etc,media,cache}
docker pull owntone/owntone

docker run -d
--name=OwnTone
--network=host
-e UID=$(id -u)
-e GID=$(id -g)
-v $HOME/OwnTone/etc:/etc/owntone
-v $HOME/OwnTone/media:/srv/media
-v $HOME/OwnTone/cache:/var/cache/owntone
--restart unless-stopped
docker.io/owntone/owntone:latest

In Portainer, it says that docker is unhealty. Do I miss something? I tried with arm64v8 tag but it doesn't work. I have 64 bit Debian.

Regards,
Stephane

@hacketiwack hacketiwack transferred this issue from owntone/owntone-server Feb 11, 2025
@hacketiwack hacketiwack reopened this Feb 11, 2025
@hacketiwack
Copy link
Collaborator

Could you please add any logs or error you might receive?
Thanks in advance.

@stephane77777
Copy link
Author

_OwnTone_logs.txt

@hacketiwack
Copy link
Collaborator

Thanks for the logs.
It seems that your instance of the container does not have access to this path:

db: Could not open '/var/cache/owntone/database.db': unable to open database file

Can you create this directory with the correct access rights, or make it point to your existing database if you have already one?

@stephane77777
Copy link
Author

It works! Thanks! I have a few questions to understand what I did wrong!

I'm logged as root on DietPi (based on Debian) : uid=0(root) gid=0(root) groups=0(root)

I ran the docker command as root
I changed Owner to dietpi:dietpi (was root) and mode to 0777 (both are recursive) was 0755 by memory

Before I tried with -e PUID=0 \ and -e PGID=0 \ without changing owner and mode
Is there any reasons why it would not work running the docker as root? Safety mesure?
Or was it only 0777 that would work (but when I try to change to 0777, it doesn't save)?
Is the docker settings of you docker different than most docker hub like daap with explains why that one worked (28.10) without changing owner or rights?

Usually, which user and mode dockers should need to run?
Should I create docker and directories under dietpi user or admin user and which rights should I choose to avoid issues?

@stephane77777
Copy link
Author

I tried to activate Spotify, it worked but I got the error (in Chrome)
Invalid token

Just to let you know.

@stephane77777
Copy link
Author

Correction, I can see spotify playlists but it fails to play any spotify songs in any plalists! It says in Chrome (after trying to autorise) : Could not find access token in Spotify reply (see log)

Does it works on your side with Spotify?

@stephane77777
Copy link
Author

_OwnTone_logs.txt

@ejurgensen
Copy link
Member

Sounds like this issue: owntone/owntone-server#1846

It's fixed, but the fix is after the 28.11 release, so I think you would need to use the staging release.

@stephane77777
Copy link
Author

Sounds like this issue: owntone/owntone-server#1846

It's fixed, but the fix is after the 28.11 release, so I think you would need to use the staging release.

Thanks for the info!

@hacketiwack
Copy link
Collaborator

Indeed, @stephane77777 you should pull the image with the tag staging instead of latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants