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

help with folder access #22

Open
michondr opened this issue Jan 17, 2025 · 0 comments
Open

help with folder access #22

michondr opened this issue Jan 17, 2025 · 0 comments

Comments

@michondr
Copy link
Contributor

I think you're runnign the stack in synology, im running in ubuntu. you might know what I did wrong though

I ran out of disk space and decided to move the whole stack to a different mounted folder.

I stopped+removed all containers, changed the folders, coppied all the files

docker compose --file docker-compose-mediastack.yaml --env-file docker-compose.env down --remove-orphans

and

FOLDER_FOR_MEDIA=/media/user/mediastack/media
FOLDER_FOR_DATA=/media/user/mediastack/data

ownerships following:

/media/user/mediastack - user:user
/media/user/mediastack/media - docker:docker
/media/user/mediastack/data - docker:docker

inside the media/data if was mishmash of docker or root for some reason. but that worked alright

I've started the stack and something was off, eg starrs didn't seem to find the configs and prompted me to start the configuration from scratch

so I started whole set of possibly not good ideas, such as recursively giving chown docker:docker ownership to the files, and then chmod 775

still didn't work.

so, now back to square one, with prorably all the configs and the media in my root

FOLDER_FOR_MEDIA=/mediastack              # <-- Update for your folders - Synology Example: /volume1/docker/appdata
FOLDER_FOR_DATA=/mediastackdata           # <-- Update for your folders - Synology Example: /volume1/media

aaand it still does not work

$ ls -la | grep mediasta
drwxr-xr-x   6 docker docker       4096 led 16 07:52 mediastack
drwxr-xr-x  18 docker docker       4096 led 16 05:28 mediastackdata

jellyfin starts but cannot connect to the server, starrs want me to do fresh setup, qbittorrent does not remember the password.
interestingly the only container whitch kept going OK is scrutiny I've added before the migration

I dont know if there was some issue where the FOLDER* variables were not set properly and didn't target the correct path, or if docker kept some volume targets.

I'd like not to start all over again with setting up the priviledges/configs/access to all the services from scratch if there is some easy answer. or some tricks so that I don't screw it up again in the future.

any ideas?

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

1 participant