Bug 46297 – The container for 4.1/horde=5.2.7-3 could not be started!

Bug 46297 - The container for 4.1/horde=5.2.7-3 could not be started!


Summary:	The container for 4.1/horde=5.2.7-3 could not be started!

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:	App Center maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-02-15 18:45 CET by Johannes Keiser
Modified:	2020-07-03 20:56 CEST (History)
CC List:	0 users

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?:	3: A User would likely not purchase the product
User Pain:	0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018012321000731
Bug group (optional):	External feedback
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Johannes Keiser

2018-02-15 18:45:01 CET

Version: 4.2-3 errata262 (Lesum)

The container for 4.1/horde=5.2.7-3 could not be started!

docker logs 542fa0a2c4a31e259fe59f87e1a0dd3130c33031e7ab947a412e294c96e07e5d:


dockerd logs:
-- Logs begin at mar. 2017-12-19 14:27:18 CET, end at mar. 2018-01-23 18:15:54 CET. --
janv. 23 12:31:08 ucs-1614 dockerd[1468]: time="2018-01-23T12:31:08.357182246+01:00" level=info msg="Docker daemon" commit=78d1802 graphdriver=overlay version=1.12.6
janv. 23 12:31:08 ucs-1614 dockerd[1468]: time="2018-01-23T12:31:08.414931497+01:00" level=info msg="API listen on /var/run/docker.sock"
-- Reboot --
janv. 23 12:58:46 ucs-1614 dockerd[1454]: time="2018-01-23T12:58:46.009247909+01:00" level=info msg="libcontainerd: new containerd process, pid: 1571"
janv. 23 12:58:52 ucs-1614 dockerd[1454]: time="2018-01-23T12:58:52.220478219+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
janv. 23 12:58:52 ucs-1614 dockerd[1454]: time="2018-01-23T12:58:52.220669209+01:00" level=warning msg="Your kernel does not support swap memory limit."
janv. 23 12:58:52 ucs-1614 dockerd[1454]: time="2018-01-23T12:58:52.221081824+01:00" level=info msg="Loading containers: start."
janv. 23 12:58:55 ucs-1614 dockerd[1454]: time="2018-01-23T12:58:55.742922382+01:00" level=info msg="Firewalld running: false"

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/4a83d1506b54df7cb6b3df56e2ec08a52b6fb345c575f64230f093041d2bd2ea/merged', u'WorkDir':
u'/var/lib/docker/overlay/4a83d1506b54df7cb6b3df56e2ec08a52b6fb345c575f64230f093041d2bd2ea/work', u'LowerDir':
u'/var/lib/docker/overlay/26c82a054ccc7ac71c9ae0d710711a0c467ceff201ffb742d6d0f318333882fe/root', u'UpperDir':
u'/var/lib/docker/overlay/4a83d1506b54df7cb6b3df56e2ec08a52b6fb345c575f64230f093041d2bd2ea/upper'}, u'Name': u'overlay'}

Comment 1 Ingo Steuwer

2020-07-03 20:56:38 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.