The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
This image has been promoted to Linuxserver proper - https://github.com/linuxserver/docker-your_spotify. This image will no longer be updated.
your_spotify is a self-hosted application that tracks what you listen and offers you a dashboard to explore statistics about it! It's composed of a web server which polls the Spotify API every now and then and a web application on which you can explore your statistics.
Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver-labs/your_spotify:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | latest |
| arm64 | ✅ | latest |
| armhf | ❌ |
You have to create a Spotify application through their developer dashboard to get your Client ID and secret. Set the Redirect URI to match your APP_URL address with /api/oauth/spotify/callback included after the domain (i.e., `http://localhost/api/oauth/spotify/callback).
The application requires an external mongodb database, supported versions are 4.x and 5.x.
This ia an all-in-one container which includes both the server and client components. If you require these to be separate then please use the releases from the your_spotify repo.
By default, Your Spotify will only retrieve data for the past 24 hours once registered. This is a technical limitation. However, you can:
- Request your privacy data at Spotify to have access to your history for the past year here. This can take up to 30 days.
- Optional: once received, you can ask for extended data that will get you your whole history. You have to email [email protected] saying you want all your data since account creation.
- Go to the settings of your account and import your StreamingHistoryX.json files.
- Now you can follow the progress of the import with the progress bar.
For more information see your_spotify.
Here are some example snippets to help you get started creating a container.
docker-compose (recommended, click here for more info)
---
version: "2.1"
services:
your_spotify:
image: lscr.io/linuxserver-labs/your_spotify:latest
container_name: your_spotify
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
- APP_URL=http://localhost
- SPOTIFY_PUBLIC=ABC123
- SPOTIFY_SECRET=XYZ098
- CORS=http://localhost:80,https://localhost:443
- MONGO_ENDPOINT=mongodb://mongo:27017/your_spotify
ports:
- 80:80
- 443:443
restart: unless-stoppeddocker cli (click here for more info)
docker run -d \
--name=your_spotify \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e APP_URL=http://localhost \
-e SPOTIFY_PUBLIC=ABC123 \
-e SPOTIFY_SECRET=XYZ098 \
-e CORS=http://localhost:80,https://localhost:443 \
-e MONGO_ENDPOINT=mongodb://mongo:27017/your_spotify \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
lscr.io/linuxserver-labs/your_spotify:latestContainer images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 80 |
HTTP port. |
-p 443 |
HTTPS port. |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Europe/London |
Specify a timezone to use EG Europe/London. |
-e APP_URL=http://localhost |
The protocol and hostname where the app will be accessed. |
-e SPOTIFY_PUBLIC=ABC123 |
Your Spotify application client ID. |
-e SPOTIFY_SECRET=XYZ098 |
Your Spotify application secret. |
-e CORS=http://localhost:80,https://localhost:443 |
Allowed CORS sources, set to all to allow any source. |
-e MONGO_ENDPOINT=mongodb://mongo:27017/your_spotify |
Set mongodb endpoint address/port. |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpasswordWill set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
- Shell access whilst the container is running:
docker exec -it your_spotify /bin/bash - To monitor the logs of the container in realtime:
docker logs -f your_spotify - container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' your_spotify
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/your_spotify
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
- Update all images:
docker-compose pull- or update a single image:
docker-compose pull your_spotify
- or update a single image:
- Let compose update all containers as necessary:
docker-compose up -d- or update a single container:
docker-compose up -d your_spotify
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- Update the image:
docker pull lscr.io/linuxserver/your_spotify - Stop the running container:
docker stop your_spotify - Delete the container:
docker rm your_spotify - Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
docker image prune
-
Pull the latest image at its tag and replace it with the same env variables in one run:
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once your_spotify
-
You can also remove the old dangling images:
docker image prune
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
- We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver-labs/docker-your_spotify.git
cd docker-your_spotify
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver-labs/your_spotify:latest .The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --resetOnce registered you can define the dockerfile to use with -f Dockerfile.aarch64.
- 30.01.23: - Promote to Linuxserver.
- 23.01.23: - Rebase to Alpine 3.17, migrate to s6v3.
- 23.02.22: - Initial Release.
