htdocs directory not populating with persistent volume #112
Comments
|
Same for me. I also tried copying the htdocs content while it was running into a mount and then making that mount the main mount, but now I just get persistent 500 errors (even with 100 user and 101 group permissions set for the folder). If I try to hit the dashboard it can't find the URL it seems: |
|
I hit the same issue. Still not solved it either. You can use persistent volumes, you just need to use a docker volume rather than a filesystem one. This is sufficing for now, but doesn't match what I usually do. services:
linkstack:
image: linkstackorg/linkstack:latest
volumes:
- mylinkstackvolume:/htdocs
<restofconfig>
volumes:
mylinkstackvolume:
And that works just fine |
|
Thanks for the info, I'll test that as a development environment. Unfortunately, I can't use it productively as my entire Docker setup is based on docker-compose.yml's that are located on Github and the data that is stored on a NAS that is backed up - I can start the restore on any system using a bash script. Let's see if the error will be fixed in time. |
can you show us the permissions inside of the Container ? |
|
Do your files have the correct permission, they should have the apache group and Name with the UID 100 and GID 101. Another error could be that the dotfiles are missing. This happend to me, becuase mv seems not to move dotfiles, if not mentioning them explicity. |
|
Hello, has anyone found a solution for that issue? Thank you all for your amazing work! (tried changing owners of the folder, even tried chmodding it to 777 as a test, and it did not work) |
|
As all things in life, I found the answer 2 minutes after my question! Note that I am using SWAG (NGINX) as my web facing proxy... so some parts for your perticular setup might need modifications... Turns-out calling the local path directly in the service definition is not working, but binding the volume to the filesystem works fine... This works for me! version: "3.8"
services:
linkstack:
hostname: linkstack
image: linkstackorg/linkstack:latest
container_name: linkstack
restart: unless-stopped
environment:
TZ: "America/Toronto"
SERVER_ADMIN: "email@domain.com"
#LOG_LEVEL: 'info'
PHP_MEMORY_LIMIT: "256M"
UPLOAD_MAX_FILESIZE: "8M"
ports:
- "8099:80"
- "8443:443"
volumes:
- "linkstack_persistent:/htdocs"
networks:
- swag-network
networks:
swag-network:
external: true
volumes:
linkstack_persistent:
driver: local
driver_opts:
o: bind
type: none
device: /your/path/linkstack |
|
@Normand-Nadon like I've written above you need to populate the latest release manually if you use a bind mount instead of a docker volume. The current docs don't mention it currently but I submitted a PR a month ago to add that |
|
It's on the Docs-Website now btw.: |
Oh, the way I did it, I did not need to populate the folders.... I have no idea why though! |
Hi together,
when i deploy the sample docker-compose.yml LinkStack works just fine but when i switch to a persistent volume, the directorys got created but not populated with any data.
My docker-compose.yml looks like this:
`version: "3.8"
services:
linkstack:
hostname: 'linkstack'
image: 'linkstackorg/linkstack:latest'
environment:
TZ: 'Europe/Berlin'
SERVER_ADMIN: 'rolf@anything.it'
HTTPS_SERVER_NAME: 'links.anything.cloud'
LOG_LEVEL: 'info'
PHP_MEMORY_LIMIT: '256M'
UPLOAD_MAX_FILESIZE: '8M'
volumes:
- /docker-centralstore/linkstack/htdocs:/htdocs/
ports:
- '8190:443'
restart: unless-stopped
volumes:
linkstack:`
Anybody have any ideas whats wrong? The Containers Log doesn't show any errors.
best regards
Rolf
The text was updated successfully, but these errors were encountered: