Nextcloud Install Error: Cron

Apps and Virtualization
1

Another noob on a mission to get something working, any help would be appreciated!

I’m having trouble installing Nextcloud, and getting an error about a repository not existing, but unsure what that means exactly.

When I cd to read app_lifecycle.log in /var/log I get


"cron Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested acces>
 nextcloud Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested

I guess I thought I was running docker by default as all apps in TrueNAS are docker files now, or is that incorrect?

Anyway, thank you in advance and excited for response!

1 Like
2

I’m getting the same error when trying to install also.

 cron Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
 nextcloud Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Wondering if something we’re doing or if it’s the repository having issues?

3

Looks like it’s something I’m doing wrong. Have been able to install using all the defaults as a test. Time to figure out what I’m doing wrong…

4

Found solution finally. Had to do with how I was setting up the Datasets.
Just needed to closely follow the instructions in the guide here: Nextcloud Deployment | TrueNAS Apps
Hope this helps if anyone else has this issue.

5

It appears I’ve having a similar issue. Also, being a noob with both Linux and TrueNAS isn’t helping.

Background
Installed TrueNAS about a week ago, and have been playing around with it. I currently have Nextcloud running on another Asustor NAS, and really wanted to migrate it to this device. It was a bit of a bumpy road, but finally got the data/database migrated, the app up and running and clients connected to the new instance.

Somewhere during the process I convered the app to a ‘custom app’ in the hopes of being able to expose the nextcloud-postgres DB container on the network. The thought was, since I needed to go through the Nextcloud db conversion process anyway, it would be better to just target the final db instance. However, in the end, I installed a separate Postgres db instance, perfrormed the Nextcloud db migration to that instance, then dumped/restored to the Postgres instance in the new Nextcloud stack. Migration was bumpy, but finally got there.

Within hours of getting the clients back up and running, I noticed a update notification, so ran the update, which failed with below error:

(ERROR) app_lifecycle.compose_action():56 - Failed 'pull' action for 'nextcloud' app:  nextcloud Skipped - Image is already being pulled by cron
 cron Pulling
 postgres Pulling
 redis Pulling
 postgres_upgrade Pulling
 permissions Pulling
 postgres_upgrade Pulled
 redis Pulled
 permissions Pulled
 cron Warning pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
 postgres Pulled
WARNING: Some service image(s) must be built from source by running:
    docker compose build cron
1 error occurred:
        * Error response from daemon: pull access denied for ix-nextcloud, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I’ve tried updating several times. After the first attempt, there were several ‘download’ lines in the log where I assume it was pulling the new images. Since then, each attempt only gets the output above, I’m assuming since the images are already pulled.

This may be exacerbated by the fact that I converted the Nextcloud app to a ‘custom app’ while initially playing with it. I saw in the UI that the conversion to a custom app is one-way. However, I’ve made no changes to the YAML code, so is there any way, under the hood, to have TrueNAS go back to the ‘standard’ config (worth a hope that I just can’t go back via the GUI, but may be able to update some files in the /mnt/.ix-apps directory to get back)?

Based on the permissions discussions earlier in the thread, I’ve tried the following on the html & data datasets:

  • Updated ACLs to make ‘apps’ (id=568) the owning id/group (was www-data (di=33))
  • Granted ‘www-data’ (id=33) full-control
  • Applied the ACLs recursively to each dataset

I’m, not seeing where I’m specifically having any permissions issues with the app at this point, but every time I try an update, if fails with the error above.

If I’ve screwed myself by converting to a custom app, can I remove/reinstall Nextcloud, using the same html/data datasets and db, WITHOUT completely disrupting the clients again?

Thanks in advance…