Shaarli - Your own Delicious

Currently reading
Shaarli - Your own Delicious

43
10
NAS
DS1019+
Router
  1. RT2600ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Hi again... I m getting crazy.. trying to start this easy docker:

$ docker create \
--name shaarli \
-v shaarli-cache:/var/www/shaarli/cache \
-v shaarli-data:/var/www/shaarli/data \
-p 8000:80 \
shaarli/shaarli:master

The Log says its ready to handle cponnections but error page when http://IP_NAS:8000

Any help please experts ??
 
1,106
362
NAS
DS418play, DS213j, DS3621+, DSM 7.0.4-11091
Check running container. Confirm port 8000 is linked w/80.
 
Uhm, did you just create it (without starting it)?

I used your exact command, followed by a docker start shaarli. When I open http://{dsm}:8000 a page opens with the title "install shaarli".
 
43
10
NAS
DS1019+
Router
  1. RT2600ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Sorry,I wrote the code, but, yes, i started it from portainer.
 
1,106
362
NAS
DS418play, DS213j, DS3621+, DSM 7.0.4-11091
Do shaarli-cache and shaarli-data exist on your NAS?

Maybe try this...
Code:
docker create -p 8000:80 shaarli/shaarli

Then start.
 
Like I wrote: it works for me.

It is never a good idea to showcase an issue with anything else than with what you actualy did. People tend to redact what they actualy did and usualy hide what actualy caused the problem.

Thus said, would you mind sharing your current container configuration with us?
 
43
10
NAS
DS1019+
Router
  1. RT2600ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
i m sorry, this is the exact code i ve run:


Code:
$ docker create \
    --name shaarli \
    -v /volume1/docker/Shaarli/cache:/var/www/shaarli/cache \
    -v /volume1/docker/Shaarli/data:/var/www/shaarli/data \
    -p 8677:80 \
    shaarli/shaarli:master
$ docker start shaarli
 
Same result: works for me. The "Install Shaarli" installation page appears right away.

First I though maybe this is one of the images that relies on the copy-on-create mechanism for volumes that copies existing data from the contaienr target folder into the volume, but the target folders are empty in the image. So this is not the problem.

The image uses a fairly uncommon folder structure for an image that uses s6-overlay. Even though the container starts with root priviliges, the nginx and php-fpm7 process are started with the restricted user nginx. The user has the UID 100 and GID 101. Since I created the host folders with mkdir -p /volume1/docker/Shaarli/{cache,data}, the permission mask for the folders is 777. Thus, the user inside the image could write files (which didn't happen because I didn't finish the installer).

You could try to check wether it makes a difference if the owner if these folders is 100:101.
If this doesn't help, then I have no idea.
 
43
10
NAS
DS1019+
Router
  1. RT2600ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Finally i found the solution !! Resstart the f#kn? Docker service and all run !!!

Thanks for your patience !
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top