search

LinkStackOrg / linkstack-docker

A simple to set up docker variant of LinkStack. LinkStack is a highly customizable link sharing platform with an intuitive, easy to use user interface.
https://linkstack.org/docker
GNU Affero General Public License v3.0
359 stars 44 forks source link

htdocs directory not populating with persistent volume #112

Open rhasselbusch opened 10 months ago

rhasselbusch commented 10 months ago

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:

volumes: linkstack:`

Anybody have any ideas whats wrong? The Containers Log doesn't show any errors.

best regards Rolf

helfrichmichael commented 10 months ago

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:

[Mon Jan 08 10:16:18.258392 2024] [core:info] [pid 36] [client 172.17.0.1:47206] AH00128: File does not exist: /htdocs/dashboard
[Mon Jan 08 10:16:18.258317 2024] [httpd.conf] 172.17.0.1 - - "GET /dashboard HTTP/1.1" 404 279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" 3240 494
[Mon Jan 08 10:16:20.276640 2024] [core:info] [pid 48] [client 172.17.0.1:47254] AH00128: File does not exist: /htdocs/dashboard
[Mon Jan 08 10:16:20.276503 2024] [httpd.conf] 172.17.0.1 - - "GET /dashboard HTTP/1.1" 404 279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" 3188 494
listerthrawn commented 10 months ago

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

rhasselbusch commented 10 months ago

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. If I now use Docker Volumes, I also have to back up the system itself or somehow rsync the local folder to the NAS or similar. - Unfortunately, that doesn't work.

Let's see if the error will be fixed in time.

lastsamurai26 commented 10 months ago

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:

[Mon Jan 08 10:16:18.258392 2024] [core:info] [pid 36] [client 172.17.0.1:47206] AH00128: File does not exist: /htdocs/dashboard
[Mon Jan 08 10:16:18.258317 2024] [httpd.conf] 172.17.0.1 - - "GET /dashboard HTTP/1.1" 404 279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" 3240 494
[Mon Jan 08 10:16:20.276640 2024] [core:info] [pid 48] [client 172.17.0.1:47254] AH00128: File does not exist: /htdocs/dashboard
[Mon Jan 08 10:16:20.276503 2024] [httpd.conf] 172.17.0.1 - - "GET /dashboard HTTP/1.1" 404 279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" 3188 494

can you show us the permissions inside of the Container ? i use my own folder für linkstack and i don't have problems

nikurasutan commented 9 months ago

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.

le-patenteux commented 8 months ago

Hello, has anyone found a solution for that issue? I prefer to have my files in a persistent filesystem storage instead of a docker volume. Simpler to backup and manage

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)

le-patenteux commented 8 months ago

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
nikurasutan commented 8 months ago

@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 https://github.com/LinkStackOrg/docs/pull/9/files#diff-bbecedccd398b5bb74ad0dff5a5174b41988214dbff19d55713f8bd97bf926e6R84

nikurasutan commented 8 months ago

It's on the Docs-Website now btw.: https://docs.linkstack.org/docker/setup/#docker-bind-mounts

le-patenteux commented 8 months ago

@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 https://github.com/LinkStackOrg/docs/pull/9/files#diff-bbecedccd398b5bb74ad0dff5a5174b41988214dbff19d55713f8bd97bf926e6R84

Oh, the way I did it, I did not need to populate the folders.... I have no idea why though!

topmask commented 5 months ago

Problem solving

le-patenteux commented 5 months ago

I'm also using nginx reverse proxy, but I have been unable to successfully reverse proxy. I don't know what the problem is. Do I need to install this swag-network?"

@topmask

Your question is completely off-topic with this issue... Here is what I see though: it seems like you are complicating things for very little... I used the default templates provided by "swag" and "swag-network" is the docker network I created for all services to communicate with the swag service.

## 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: linkstack

EDIT:

One last note, when using swag, don't edit the master nginx proxy.conf... you simply make a copy of the example file linkstack.subdomain.conf.sample in the proxy-confs folder and remove the .sample at the end of the file

topmask commented 5 months ago

I'm also using nginx reverse proxy, but I have been unable to successfully reverse proxy. I don't know what the problem is. Do I need to install this swag-network?"

@topmask

Your question is completely off-topic with this issue... Here is what I see though: it seems like you are complicating things for very little... I used the default templates provided by "swag" and "swag-network" is the docker network I created for all services to communicate with the swag service.

## 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: linkstack

EDIT:

One last note, when using swag, don't edit the master nginx proxy.conf... you simply make a copy of the example file linkstack.subdomain.conf.sample in the proxy-confs folder and remove the .sample at the end of the 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.

pixelrazor commented 5 days ago

What's the possibility of having the docker image either fetch or include everything? Is there an argument against either option?

JulianPrieber commented 4 days ago

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. We recommend using a volume for persistent storage.

pixelrazor commented 4 days ago

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. We recommend using a volume for persistent storage.

Sorry, I didn't specify - in particular, I meant when using a bind mount