About the not answering with Y part... I noticed that and when I tried to run this process a second time I did it right. I thought I had edited my post to take that bit out.
I appreciate your help. I may try to fix it one last time just to see if it works without the plugin, but I believe that I am just going to make this a retro pie for now to replace my hacked SNES mini and start again with something that is more powerful in the future.
Typing in
apt-get purge docker-ce
Gives me this:
The next few lines worked until,
apt-get purge cockpit-docker docker-ce-cli
Gives me this:
Then finally,
apt-get install docker-ce
returns:
Once again I started with a brand new install. The only things I have done are as follows:
Flashed the SD card.
Waited until the Pi wasn't showing any more scrolling text and logged into the webui.
Changed autologout to disable, and default password.
Fixed date/time.
Enabled permit root login in SSH
Changed root password via putty.
update/upgrade
Enabled Docker CE in extras.
Installed docker gui, which fails.
Typed in commands you gave me.
I will try these steps in a couple of hours and get back with you.
At this point I think that I am just going to install Raspbian on this Pi so I can get it up and running for what I need right now. I may come back to OMV in the future when I get something else to run it on.
Yes. I tried all the steps you outlined in an earlier reply more than once because you said it wouldn't hurt to run them more than once.
I have also reformatted and tried a fresh install again more than once.
If it matters any, other than my issues installing Docker, OMV is up and running currently and sharing a single HDD on my network.
What is your error when just installing docker-ce?
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
containerd.io docker-ce-cli
Recommended packages:
aufs-tools cgroupfs-mount | cgroup-lite pigz
The following NEW packages will be installed:
containerd.io docker-ce docker-ce-cli
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 29.6 MB of archives.
After this operation, 148 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://download.docker.com/linux/debian stretch/stable armhf containerd.io armhf 1.2.4-1 [10.7 MB]
Get:2 https://download.docker.com/linux/debian stretch/stable armhf docker-ce-cli armhf 5:18.09.3~3-0~debian-stretch [8,091 kB]
Get:3 https://download.docker.com/linux/debian stretch/stable armhf docker-ce armhf 5:18.09.3~3-0~debian-stretch [10.8 MB]
Fetched 29.6 MB in 7s (4,210 kB/s)
Selecting previously unselected package containerd.io.
(Reading database ... 51484 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.2.4-1_armhf.deb ...
Unpacking containerd.io (1.2.4-1) ...
Selecting previously unselected package docker-ce-cli.
Preparing to unpack .../docker-ce-cli_5%3a18.09.3~3-0~debian-stretch_armhf.deb ...
Unpacking docker-ce-cli (5:18.09.3~3-0~debian-stretch) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a18.09.3~3-0~debian-stretch_armhf.deb ...
Unpacking docker-ce (5:18.09.3~3-0~debian-stretch) ...
Setting up containerd.io (1.2.4-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up docker-ce-cli (5:18.09.3~3-0~debian-stretch) ...
Setting up docker-ce (5:18.09.3~3-0~debian-stretch) ...
update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2019-03-20 21:07:47 EDT; 26ms ago
Docs: https://docs.docker.com
Process: 8337 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 8337 (code=exited, status=1/FAILURE)
CPU: 632ms
Mar 20 21:07:47 raspberrypi systemd[1]: docker.service: Unit entered failed state.
Mar 20 21:07:47 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
dpkg: error processing package docker-ce (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u9) ...
Errors were encountered while processing:
docker-ce
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x762cc390>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x762cc390>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am having the exact same problems, and errors as listed on this thread and the solutions posted above are not helping.
I am working with a brand new RPi 3b+ though.
I was following TechnoDadLife's video posted in the sticky on this forum on setting up when I errored out at the install of Docker.
