mhynlo / readynas-docker-cli Goto Github PK

When attempting to uninstall the package the ReadyNAS frontend returns an error and fails to remove the package.

Any chance for support for ReadyNAS on Intel Atom chip?

Intel(R) Atom(TM) CPU D405

# uname -a
Linux gasgiant 4.4.79.x86_64.1 #1 SMP Mon Jul 31 15:14:40 PDT 2017 x86_64 GNU/Linux

As this Add-on is not really being kept up to date, what are the proper steps to manually update docker to the latest version. I can find out from docker resources how to do that, but I am unclear about what is different in the way this readynas add-on is setup compared to a normal docker installation, that might effect the way I attempt to do that.

Please advise!

Does installing this through the readynas admin page install docker, or is this a cli client wrapper you've written for docker?

I'd like to install docker and manage it through ssh access, but I'm having trouble tracking down any documentation. Thanks!

Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: fv-app-install (/tmp/docker-cli-rnapp_17.06.0_amd64.deb): error code [100]: Reading package lists...
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: Building dependency tree...
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: Reading state information...
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: Some packages could not be installed. This may mean that you have
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: requested an impossible situation or if you are using the unstable
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: distribution that some required packages have not yet been created
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: or been moved out of Incoming.
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: The following information may help to resolve the situation:
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: The following packages have unmet dependencies:
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: docker-cli-rnapp : Depends: linux-image-extra but it is not going to be installed
Aug 10 18:26:30 ReadyNAS1 fv-app-install[13128]: E: Unable to correct problems, you have held broken packages.
Aug 10 18:26:31 ReadyNAS1 fv-app-install[13128]: docker-cli-rnapp abort
Aug 10 18:26:31 ReadyNAS1 readynasd[3984]: spooler (pid=13124) returns spool_status=1 outbuf=(null) errbuf=(null) is_localapp=1 name=docker-cli-rnapp pkgname=docker-cli-rnapp

The title says it all :).

root@ReadyNAS:~# systemctl status docker.socket
● docker.socket - Docker Socket for the API
   Loaded: loaded (/lib/systemd/system/docker.socket; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2017-06-24 13:03:51 CEST; 7min ago
   Listen: /var/run/docker.sock (Stream)

Jun 24 13:03:51 ReadyNAS systemd[1]: Starting Docker Socket for the API.
Jun 24 13:03:51 ReadyNAS systemd[1]: docker.socket: Control process exited, code=exited status=216
Jun 24 13:03:51 ReadyNAS systemd[1]: Failed to listen on Docker Socket for the API.
Jun 24 13:03:51 ReadyNAS systemd[1]: docker.socket: Unit entered failed state.

root@ReadyNAS:~# cat /etc/group | grep docker
Pattern not found

root@ReadyNAS:~# groupadd docker

root@ReadyNAS:~# systemctl start docker.socket

root@ReadyNAS:~# systemctl status docker.socket
● docker.socket - Docker Socket for the API
   Loaded: loaded (/lib/systemd/system/docker.socket; disabled; vendor preset: enabled)
   Active: active (listening) since Sat 2017-06-24 13:11:30 CEST; 9min ago
   Listen: /var/run/docker.sock (Stream)

Jun 24 13:11:30 ReadyNAS systemd[1]: Starting Docker Socket for the API.
Jun 24 13:11:30 ReadyNAS systemd[1]: Listening on Docker Socket for the API.`

Could you add the groupadd statement as part of the install script?

Amy chance there will be support for a version on ARM for use on a readynas 102?

Hello,

how is it possible to change the volumes location permanently?
I tried to change the docker.service files but it doesn't work.

/apps/docker-cli-rnapp/volumes/test2/_data

It keeps generating volumes under the app directory which is bad because there are no default backups possible.

Thanks

Thorsten

Installed latest version, which reports as 18.06.3 (both in installed apps on the NAS and in SSH), though it showed an earlier version under "available apps" when I installed. But the Launch button is ghosted. Installed on ReadyNASOS 6.10.1 on x64 based virtual machine (where I test everything before installing for real). Tried toggling off/on and re-boot, neither helped.