Installed Docker, but it won't run / start

inspiredearth

I installed Docker using the Docker Manager in Cyber 2.0 Build 1.

But Docker service won't start.

Is there something else I need to do to make Docker Manager run?

inspiredearth

To see what's going on, I tried $docker -- info

Got the following output:

- - - -
Client:
Debug Mode: false

Server:
ERROR: error during connect: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/info: read unix @->/var/run/docker.sock: read: connection reset by peer
errors pretty printing info
- - - -

I tried to start docker on command line

- - - - - -
$sudo systemctl start docker
A dependency job for docker.service failed. See 'journalctl -xe' for details.
- - - - - -

Here's the content from journalctl -xe , after I tried to start Docker on the command line:

- - - - - - - -
-- Subject: Process /usr/bin/containerd could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /usr/bin/containerd could not be executed and failed.
--
-- The error number returned by this process is 1.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Main process exited, code=exited, status
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Service hold-off time over, scheduling r
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Scheduled restart job, restart counter i
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit containerd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Stopped containerd container runtime.
-- Subject: Unit containerd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has finished shutting down.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Start request repeated too quickly.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Failed to start containerd container runtime.
-- Subject: Unit containerd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has failed.
--
-- The result is RESULT.
Sep 16 01:09:16 inspiredearth.nz sudo[2247]: inspired : TTY=pts/0 ; PWD=/home/inspired ; USER=root ; COMM
Sep 16 01:09:16 inspiredearth.nz sudo[2247]: pam_unix(sudo:session): session opened for user root by insp
lines 3182-3216/3216 (END)
-- Subject: Process /usr/bin/containerd could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /usr/bin/containerd could not be executed and failed.
--
-- The error number returned by this process is 1.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Main process exited, code=exited, status=205/LIMITS
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Service hold-off time over, scheduling restart.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit containerd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Stopped containerd container runtime.
-- Subject: Unit containerd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has finished shutting down.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Start request repeated too quickly.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Failed to start containerd container runtime.
-- Subject: Unit containerd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has failed.
--
-- The result is RESULT.
lines 3182-3214/3216 100%
-- Subject: Process /usr/bin/containerd could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /usr/bin/containerd could not be executed and failed.
--
-- The error number returned by this process is 1.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Main process exited, code=exited, status=205/LIMITS
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Service hold-off time over, scheduling restart.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit containerd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Stopped containerd container runtime.
-- Subject: Unit containerd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has finished shutting down.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Start request repeated too quickly.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: containerd.service: Failed with result 'exit-code'.
Sep 16 01:09:04 inspiredearth.nz systemd[1]: Failed to start containerd container runtime.
-- Subject: Unit containerd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit containerd.service has failed.
--
-- The result is RESULT.

inspiredearth

I was able to get Docker running at the commend line with command `dockerd`.

It now allows me to manage containers in Docker Manager.

But I can't restart or stop the service in Service Status in CP.
So there's still something wrong in the way the installation played out.

inspiredearth

After setting up the container, I see these errors in the container log, after trying to Run the container:

cp: can't stat '/var/www/app/public/assets': Permission denied
cp: can't stat '/var/www/app/public/css': Permission denied
cp: can't stat '/var/www/app/public/favicon.ico': Permission denied
cp: can't stat '/var/www/app/public/flutter_service_worker.js': Permission denied
cp: can't stat '/var/www/app/public/images': Permission denied
cp: can't stat '/var/www/app/public/index.html': Permission denied
cp: can't stat '/var/www/app/public/index.php': Permission denied
cp: can't stat '/var/www/app/public/js': Permission denied
cp: can't stat '/var/www/app/public/main.dart.js': Permission denied
cp: can't stat '/var/www/app/public/main.dart.js.map': Permission denied
cp: can't stat '/var/www/app/public/manifest.json': Permission denied
cp: can't stat '/var/www/app/public/mix-manifest.json': Permission denied
cp: can't stat '/var/www/app/public/robots.txt': Permission denied
cp: can't stat '/var/www/app/public/svg': Permission denied