Ok it all seems to be working now. Thank you all for your help!
Beiträge von teslabean
-
-
In the end I decided to reformat my external harddrive as ext4. However, having followed the guide again, using docker commands in the terminal, I still get issues. Here is the output from docker logs -f nextcloudpi:
CodeInitializing empty volume.. /run-parts.sh: line 47: /etc/services-enabled.d//etc/services-enabled.d: No such file or directory Init doneI seem to have made progress by just deleting the docker container and re-running the docker command for creating the container (nextcloud is installed and initialised). I'll see if I can get through the nextcloud activation stage tomorrow and let you know how it goes. Thanks for the help so far!
-
I would rather not reformat to ext4 if I can avoid it. Is there a way to get this working with the on the NTFS filesystem?
In the end I decided to reformat my external harddrive as ext4. However, having followed the guide again, using docker commands in the terminal, I still get issues. Here is the output from docker logs -f nextcloudpi:
CodeInitializing empty volume.. /run-parts.sh: line 47: /etc/services-enabled.d//etc/services-enabled.d: No such file or directory Init done -
I would suggest to delete the nextcloudpi folder and start fresh and stick to the guide and run it via the command line. You can manage the docker afterwards in portainer.
I tried that, and I get the same problem.
That is the issue you're looking for. They currently belong to root. You can fix that by navigating to the path and executing chown www-data:users -r .
I also tried that, using the command chown www-data:users -R config/ but the directory remained as root ownership. After doing a bit more searching online I think the problem might be that the drive I'm trying to use is NTFS formatted, so there's no concept of unix users. I would rather not reformat to ext4 if I can avoid it. Is there a way to get this working with the on the NTFS filesystem?
-
I'm attempting to install nextcloud on my Rasbperry Pi 4 using the Techno Dad Life guide "Easiest Nextcloud Installation with Docker", but using the portainer web GUI rather than through docker on the command line. I've got to the NextCloudPi activation stage and click the "activate" button, but it says "Something went wrong. Try refreshing the page". I then checked the docker logs with 'sudo docker logs -f nextcloudpi' and this is what I get:
CodeInitializing empty volume.. Making /usr/local/etc/ncp-config.d persistent ... Making /etc/services-enabled.d persistent ... Making /etc/letsencrypt persistent ... Making /etc/shadow persistent ... Making /etc/cron.d persistent ... Making /etc/cron.daily persistent ... Making /etc/cron.hourly persistent ... Making /etc/cron.weekly persistent ... Making /usr/local/bin persistent ... Making /etc/apache2 persistent ... Starting PHP-fpm Starting Apache Starting mariaDB 2020-07-13 15:46:38 0 [Note] mysqld (mysqld 10.3.22-MariaDB-0+deb10u1) starting as process 195 ... Starting Redis Starting Cron Starting Postfix Uninitialized instance, running nc-init... Running nc-init Setting up a clean Nextcloud instance... wait until message 'NC init done' Setting up database... Setting up Nextcloud... Console has to be executed with the user that owns the file config/config.php Current user: www-data Owner of config.php: root Try adding 'sudo -u root ' to the beginning of the command (without the single quotes) If running with 'docker exec' try adding the option '-u root' to the docker command (without the single quotes) Init doneIt seems to be a problem with user permissions. However, I don't know how to do what it suggests, as I can't find out how to run a portainer container as 'root'. Could someone point me in the right direction please?
-
Thanks for the help everyone, in the end I decided to change my approach; I installed borgbackup on a separate raspberry pi and then used that to execute remote backups, with the backup archives stored on my external drive (accessed via openmediavault).
-
Could someone suggest another incremental backup tool that I could use to backup files over ssh, but that can easily be installed on OMV? I've tried 'backintime' too but I had issues installing it on OMV
-
have a look at omv-extras.org for additional plugins for omv
Thanks, in the end I had to enable the "Docker CE" repository in the "OMV extras" tab to get the docker plugin to show up in the search.
-
sorry but I do not understand why you don't install dockers using webGUI and docker pluging
I searched for docker in the plugins but nothing came up. Anyway, I've got it installed now, but it seems that the issue is that there isn't a docker image of duplicity compatible with the arm/raspberry-pi architecture.
-
I installed docker with 'sudo apt-get install docker' but when I run docker it says 'command not found'
Ok, I managed to install docker using the following command: 'sudo curl -sSL https://get.docker.com/ | sh'.
However, now when I try to run the duplicity docker image:
Codedocker run --rm wernight/duplicity duplicity --helpI get the following error:
Zitatstandard_init_linux.go:207: exec user process caused "exec format error"
-
beter try to use duplicity docker, have less troubles to run on a woking enviroment.
I installed docker with 'sudo apt-get install docker' but when I run docker it says 'command not found'
-
Hi,
I've been trying to install python-dev (which I apparently need for installing paramiko, which itself is needed for duplicity) using the following command:
Codesudo pip install python-devbut I get the following error:
ZitatAlles anzeigenSome packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
python-dev : Depends: libpython-dev (= 2.7.13-2) but it is not going to be installed
Depends: python2.7-dev (>= 2.7.13-1~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.I tried the following solution detailed in here about adding the 'precise-updates' repository:
Codeecho "deb http://us.archive.ubuntu.com/ubuntu/ precise-updates main restricted" | sudo tee -a /etc/apt/sources.list.d/precise-updates.list sudo apt-get update sudo apt-get install python2.7-dev
but I then got the following error:ZitatAlles anzeigenErr:21 http://us.archive.ubuntu.com/ubuntu precise-updates armhf Contents (deb)
404 Not Found [IP: 91.189.91.23 80]
Ign:20 http://us.archive.ubuntu.com/ubuntu precise-updates/main armhf Packages
Fetched 55.7 kB in 10s (5,508 B/s)
Reading package lists... Done
W: GPG error: http://us.archive.ubuntu.com/ubuntu precise-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
W: The repository 'http://us.archive.ubuntu.com/ubuntu precise-updates InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://us.archive.ubuntu.com/u…se-updates/Contents-armhf 404 Not Found [IP: 91.189.91.23 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
