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 protected]"
#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! |
|
Problem solving |
Your question is completely off-topic with this issue... ## Version 2023/06/27
# make sure that your dns has a cname set for linkstack and that your linkstack container is not using a base url
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name links.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app linkstack;
set $upstream_port 443;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
}
Also, in your compose, you need to set the container name if you want to call it by its name in the proxy... container_name: linkstackEDIT: One last note, when using swag, don't edit the master nginx proxy.conf... you simply make a copy of the example file |
Thank you, I just want to use Nginx as a reverse proxy, but I haven't found a suitable method to handle it. I have tried all configurations but none of them work. |
|
What's the possibility of having the docker image either fetch or include everything? Is there an argument against either option? |
The docker image includes all files required to run LinkStack. |
Sorry, I didn't specify - in particular, I meant when using a bind mount |
|
I'm running into this issue as well on Unraid. I tried to run a second instance of Linkstack. The first instance was created some time ago and works fine. The second instance is having an issue generating the necessary files in /htdocs. Same settings as the one that works with the same folder permissions (except for ports). I had to download the files and put them in the folder to make this work. |
|
For custom mounts that are not based on volumes, you must place the files in this folder yourself because the Docker itself has no right to do so. |
|
I have copied the files manually into /htdocs but it still complains missing permissions. [Sun Mar 09 13:35:35.925124 2025] [php:error] [pid 37] [client 127.0.0.1:42930] PHP Fatal error: Uncaught ErrorException: file_put_contents(/htdocs/storage/framework/views/ad546639aec97f004fa1afd1e049a146a4a7f17e.php): Failed to open stream: Permission denied in /htdocs/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:190 |
|
did you used |
|
Also having the same problem, If anyone needs it this works to copy what you need into the mounted volume, im still getting the 500 error even after setting the permissions and chown. |
|
Ok i fixed it! I think its related to the Heres what id set in the manually created Then i had to trigger the following to generate the key However I was then getting some errors and it turns out it needed a database, so heres the compose im using with mariaDB: A sidenote here is im using nginx to do a proxy pass and letting it handle the SSL. Lastly, a database migrate: ... and its working! Hope that helps someone else. |
|
Updated note: youll also need a |
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: '[email protected]'
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: