Adding extensions to FreshRSS in a Docker container? #37
Comments
|
It's probably the permissions. Did you check what they are? |
|
@obsoletenerd : I believe it is simply that your Docker command is wrong. sudo docker exec -it freshrss shIt works for me in Docker, even with the default user. |
|
With the command you have run, you now probably have several FreshRSS instances running... Try: sudo docker ps -a
sudo docker rm -f ...P.S.: What you were doing is spinning a new FreshRSS instance, make the changes in that new one, and stop it (without removing it) on exit. Therefore you could not see your changes in your true instance. |
|
I must second this issue. Everything is loaded correctly, in the correct place and with correct permissions. The extension does not show up in FreshRSS. Using |
|
@DOFfactory What docker run command are you using? Are you using a Docker volume for the extensions? |
|
Hi @Alkarex, nothing extra, the standard command from linuxserver.io: |
|
The current docker image looks for extentions in |
|
You should probably install the extensions in a volume on the host, then mount it in your container. You should not add them in a running container or they risk to be dropped when you stop it. Quick example: $ mkdir /path/to/extensions
$ # install your extensions in /path/to/extensions as you do usually
$ docker run \
--rm \
--volume /path/to/data:/var/www/FreshRSS/data:z \
--volume /path/to/extensions:/var/www/FreshRSS/extensions:z \
--publish 127.0.0.1:80:80 \
--name freshrss \
freshrss/freshrss(to adapt for the The main drawback of this technique is that you have to reinstall the default extensions in the host volume (at the moment, only Tumblr-GDPR) |
|
We should improve this process. I will try to find time to make a proposition |
|
Hi, I can confirm this works. One comment: the folder must be outside on the host of the docker (naturally), but in case somebody is wondering why is it not working. I agree with @Alkarex that this has to be done nicer, the best would be some clickable "upload" function of extensions through the frontend. It would be lovely to add also url there to download/upload an extension. |
|
There is now a distinction between core extensions shipped with FreshRSS, and third-party extensions installed by the user. This makes it easier to mount a Docker volume. Implemented in the /master branch with FreshRSS/FreshRSS#2837 |
|
I am not able to get extension to run inside a docker container, therefore I reopen this issue. The theoretical steps are kinda straight forward, so here is what I did:
But nothing shows up Is there something that I do wrong? |
|
Can you try the following command? docker exec freshrss ls -alh /var/www/FreshRSS/extensions |
|
|
Right, then: docker exec freshrss chown www-data:www-data -R /var/www/FreshRSS/extensions
docker exec freshrss chmod g+rx /var/www/FreshRSS/extensions |
|
Thank you, that has worked. I went into the UI and activated the extensions (all three of them), but they show no effect (no reading time nor email sharing). Am I still missing some detail? |
|
@nickelswitte you need to bind a folder to the docker (if you use it that way) and install the extensions in that subfolder afaik |
|
@nickelswitte body {
color:red;
}
|
To ease adding custom extensions such as in FreshRSS/Extensions#37 (comment)
To ease adding custom extensions such as in FreshRSS/Extensions#37 (comment)
thank you for this.. I changed my volume to this and that did the trick ! |
This is probably a stupid question, but this is my first time playing with Docker and I can't get this to work. I installed FreshRSS into a Docker container on a Raspberry Pi, and it all works fine. Then I follow the Docker guide to access the container:
$ docker run -it freshrss/freshrss shWhich gives me a shell in
/var/www/FreshRSS/in the container.I add the extension to the
/extensionsdirectory:Then visit
http://192.168.x.x:8080/i/?c=extensionand the new extension doesn't show up?I tried
docker restart freshrss(aka turning it off and on again ;)) but still no luck.Thanks in advance.
The text was updated successfully, but these errors were encountered: