Bug 44668 - The container for 4.1/nextcloud=11.0.3-0 could not be started!
The container for 4.1/nextcloud=11.0.3-0 could not be started!
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.2-x
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-23 16:40 CEST by Florian Best
Modified: 2018-10-26 18:03 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number: 2018101821001081, 2018022821000425, 2017052321000565
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2017-05-23 16:40:26 CEST
Version: 4.2-0 errata15 (Lesum)

Remark: nach Deinstallation, neu Installation vorgenommen.

Error:
The container for 4.1/nextcloud=11.0.3-0 could not be started!

docker logs bbe38ee907bc795f453bc0881ab2d6381e8441e84dfcfa43f53e5d4b977d6766:


dockerd logs:
-- Logs begin at Di 2017-05-23 16:13:45 CEST, end at Di 2017-05-23 16:30:46 CEST. --
Mai 23 16:14:24 server dockerd[2066]: time="2017-05-23T16:14:24.099136445+02:00" level=info msg="libcontainerd: new containerd process, pid: 2146"
Mai 23 16:14:30 server dockerd[2066]: time="2017-05-23T16:14:30.058423480+02:00" level=info msg="Graph migration to content-addressability took 0.26 seconds"
Mai 23 16:14:30 server dockerd[2066]: time="2017-05-23T16:14:30.058997911+02:00" level=warning msg="Your kernel does not support swap memory limit."
Mai 23 16:14:30 server dockerd[2066]: time="2017-05-23T16:14:30.069259349+02:00" level=info msg="Loading containers: start."
Mai 23 16:14:30 server dockerd[2066]: .time="2017-05-23T16:14:30.765972094+02:00" level=info msg="Firewalld running: false"
Mai 23 16:14:37 server dockerd[2066]: time="2017-05-23T16:14:37.237224206+02:00" level=info msg="Loading containers: done."
Mai 23 16:14:37 server dockerd[2066]: time="2017-05-23T16:14:37.273113031+02:00" level=info msg="Daemon has completed initialization"
Mai 23 16:14:37 server dockerd[2066]: time="2017-05-23T16:14:37.273490391+02:00" level=info msg="Docker daemon" commit=78d1802 graphdriver=overlay version=1.12.6
Mai 23 16:14:37 server dockerd[2066]: time="2017-05-23T16:14:37.295601088+02:00" level=info msg="API listen on /var/run/docker.sock"
Mai 23 16:24:10 server dockerd[2066]: time="2017-05-23T16:24:10.647281903+02:00" level=error msg="Error setting up exec command in container 6eb31dab78cbd5e18c9abe62bbf870e6610054e0f4867c0486882493ca87545f: Container 6eb31dab78cbd5e18c9abe62bbf870e6610054e0f4867c0486882493ca87545f is not running"

docker inspect:
{u'Status': u'created', u'Pid': 0, u'OOMKilled': False, u'Dead': False, u'Paused': False, u'Running': False, u'FinishedAt': u'0001-01-01T00:00:00Z', u'Restarting': False, u'Error': u'', u'StartedAt': u'0001-01-01T00:00:00Z', u'ExitCode': 0}
{u'Data': {u'MergedDir': u'/var/lib/docker/overlay/c8b84af8449689542a050e34098cc4d8eee81a4b6827893535931e3f2b373fda/merged', u'WorkDir': u'/var/lib/docker/overlay/c8b84af8449689542a050e34098cc4d8eee81a4b6827893535931e3f2b373fda/work', u'LowerDir': u'/var/lib/docker/overlay/d6366831cedeae2e40577e407b635c354419edd37e7530230ed3eab2cc4be2e6/root', u'UpperDir': u'/var/lib/docker/overlay/c8b84af8449689542a050e34098cc4d8eee81a4b6827893535931e3f2b373fda/upper'}, u'Name': u'overlay'}
Comment 1 Felix Botner univentionstaff 2017-07-06 17:56:45 CEST
This

            "StartedAt": "0001-01-01T00:00:00Z",
            "FinishedAt": "0001-01-01T00:00:00Z"

is a clear sign that the container was never started. I suspect a systemd|sysvinit problem. Next step: prioritize trello card "App Container kann nicht gestartet werden!"
Comment 2 Felix Botner univentionstaff 2017-07-06 17:57:46 CEST
(In reply to Felix Botner from comment #1)
> This
> 
>             "StartedAt": "0001-01-01T00:00:00Z",
>             "FinishedAt": "0001-01-01T00:00:00Z"
> 
> is a clear sign that the container was never started.

more accurate "docker start container" was never executed
Comment 3 Johannes Keiser univentionstaff 2018-04-27 14:02:47 CEST
Reported again: Version: 4.2-3 errata305 (Lesum)

The container for 4.1/owncloud=10.0.4-20171212 could not be started!

docker inspect:
{u'Status': u'created', u'Pid': 0, u'OOMKilled': False, u'Dead': False, u'Paused': False, u'Running': False, u'FinishedAt': u'0001-01-01T00:00:00Z', u'Restarting': False, u'Error':
u'', u'StartedAt': u'0001-01-01T00:00:00Z', u'ExitCode': 0}
...
Comment 4 Johannes Keiser univentionstaff 2018-10-26 18:03:19 CEST
Reported again: Version: 4.3-2 errata285 (Neustadt)

The container for 4.1/nextcloud=13.0.7-0 could not be started!

docker logs 851bc2058765052e82562ad54c30150abea1af8c4103a01eb5ea35df9c5d5760:


dockerd logs:
-- Logs begin at Sun 2018-10-14 00:26:35 CEST, end at Thu 2018-10-18 20:34:35 CEST. --
Okt 18 18:58:48 nvserver dockerd[1566]: time="2018-10-18T18:58:48.505203387+02:00" level=info msg="Daemon has completed initialization"
Okt 18 18:58:48 nvserver dockerd[1566]: time="2018-10-18T18:58:48.505254709+02:00" level=info msg="Docker daemon" commit=092cba3 graphdriver=overlay version=1.13.1


docker inspect:
{u'Status': u'created', u'Pid': 0, u'OOMKilled': False, u'Dead': False, u'Paused': False, u'Running': False, u'FinishedAt': u'0001-01-01T00:00:00Z', u'Restarting': False, u'Error':
u'', u'StartedAt': u'0001-01-01T00:00:00Z', u'ExitCode': 0}
{u'Data': {u'MergedDir': u'/var/lib/docker/overlay/717870d2672a34d99e154f317aa5e1ffb9a9bede0171097ad21178fddeb7df2d/merged', u'WorkDir':
u'/var/lib/docker/overlay/717870d2672a34d99e154f317aa5e1ffb9a9bede0171097ad21178fddeb7df2d/work', u'LowerDir':
u'/var/lib/docker/overlay/e680cd3d6359ba96527bcb27a9f3ae3d5cf7d79e741ca0d911e8e4fe6da47c54/root', u'UpperDir':
u'/var/lib/docker/overlay/717870d2672a34d99e154f317aa5e1ffb9a9bede0171097ad21178fddeb7df2d/upper'}, u'Name': u'overlay'}

Role: domaincontroller_master