bj___

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by bj___

  1. @Squid I've a problem with how a docker container is restarted in the auto update plugin. If I read your code correctly you are using the docker update feature of the official Web UI to update a docker which also stops/starts the container as required. However after that is done you are restarting the docker again with a `docker start $containerScript` or a custom script if available. No problems with the custom script but is the docker start line really needed? I've some post exec arguments in the container definition which must be applied and is not regarded by just by manually using `docker start`. I know that I can supply my own script though my question is whether this restart is really needed at that point. Cheers!
  2. I just added in the "Post Arguments" box the following to install ffmpeg into the nextcloud container after it has been started: && docker exec -u root nextcloud bash -c "apt update && apt install -y ffmpeg" The "&&" causes the docker run command to finish and upon success executes what comes after it as a new command. You can put in whatever you like. Works for me, hopefully it works for others as well. But I agree that maybe another script box would be nicer and cleaner.
  3. This affects me a lot, since I'm backing up my personal data onto my shares and I'm working alot with symlinks which on my share are often not pointing to valid files, but when put into the right context will be valid again. The mover should not ignore invalid symlinks and just move them as well. Whether they are broken or not is the problem of the one who created them.
  4. You should follow the guide from nextcloud: https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/db_conversion.html
  5. Okay I found it. Since Nextcloud 22.1.0 the server code is setting explicit file permissions ignoring the umask of the system. This is unfortunate for us since without a patch there wont be an easy workaround. Here is the merge which pulled in the changes: https://github.com/nextcloud/server/commit/f3738eeff70ead6657149fa5d25bfde04f731746
  6. I moved now from LSIO to this image and everything so far works fine. Except the one thing that I also was unable to achieve with the LSIO image, the file permissions are incorrect so that I cannot write them using smb. I setup ever thing exactly like in the first post and the umask is 000, that I double checked still everything is read only. Any help is appreciated!