Bug 48578 - The container for zammad=2.6.0-31 could not be started!
The container for zammad=2.6.0-31 could not be started!
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-31 19:36 CET by Johannes Keiser
Modified: 2021-05-14 16:33 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
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.086
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018110721001009
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 Johannes Keiser univentionstaff 2019-01-31 19:36:24 CET
Version: 4.3-2 errata298 (Neustadt)

The container for zammad=2.6.0-31 could not be started!

docker logs bc9a16a11d444953c21e639ff13e9601774d694c01b0e5352625a7cde20fb23e:


dockerd logs:
-- Logs begin at Wed 2018-11-07 12:59:14 CET, end at Wed 2018-11-07 14:55:24 CET. --
Nov 07 14:45:07 ion4-backup dockerd[1394]: time="2018-11-07T14:45:07.882149735+01:00" level=info msg="Translating \"denied: requested access to the resource is denied\" to
\"repository monotek/zammad-docker-univention not found: does not exist or no pull access\""
Nov 07 14:45:07 ion4-backup dockerd[1394]: time="2018-11-07T14:45:07.882543040+01:00" level=error msg="Handler for POST /v1.26/images/create returned error: repository
monotek/zammad-docker-univention not found: does not exist or no pull access"


docker inspect:
{u'Status': u'exited', u'Pid': 0, u'OOMKilled': False, u'Dead': False, u'Paused': False, u'Running': False, u'FinishedAt': u'2018-11-07T13:55:21.911144453Z', u'Restarting': False,
u'Error': u'', u'StartedAt': u'2018-11-07T13:55:21.794912869Z', u'ExitCode': 0}
{u'Data': {u'MergedDir': u'/var/lib/docker/overlay/9dafc34da591f4ec050ee72d8f7ba0da352ef48db5c3278867fe6491e45cf701/merged', u'WorkDir':
u'/var/lib/docker/overlay/9dafc34da591f4ec050ee72d8f7ba0da352ef48db5c3278867fe6491e45cf701/work', u'LowerDir':
u'/var/lib/docker/overlay/d90bec61e7d38a3aaa47f4080827f140d29d55c2d7c60d71428cef661ef1a4d1/root', u'UpperDir':
u'/var/lib/docker/overlay/9dafc34da591f4ec050ee72d8f7ba0da352ef48db5c3278867fe6491e45cf701/upper'}, u'Name': u'overlay'}

Role: domaincontroller_backup
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:41:01 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 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.