mirror of
https://github.com/RD17/ambar.git
synced 2026-04-25 07:25:55 +03:00
[GH-ISSUE #91] ERROR: readlink /var/lib/docker/overlay2: invalid argument #90
Labels
No labels
$$ Paid Support
bug
bug
enhancement
help wanted
invalid
pull-request
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ambar#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @neergttocsdivad on GitHub (Nov 8, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/91
New installation appeared to go well, then error message:
I would greatfully appreciate any ideas how to resolve
ERROR: readlink /var/lib/docker/overlay2: invalid argument
Traceback (most recent call last):
File "./ambar.py", line 300, in
start(configuration)
File "./ambar.py", line 241, in start
runShellCommandStrict('docker-compose -f {0}/docker-compose.yml -p ambar up -d'.format(PATH))
File "./ambar.py", line 63, in runShellCommandStrict
subprocess.check_call(command, shell = True)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'docker-compose -f /home/d/docker-compose.yml -p ambar up -d' returned non-zero exit status 1
@neergttocsdivad commented on GitHub (Nov 9, 2017):
reinstalled on laptop running ubuntu 16.04 arm64 desktop and also ubuntu 16.04 arm64 server with same results, so consistently incompetent. please help.
@neergttocsdivad commented on GitHub (Nov 10, 2017):
When I wrote my previous comment, I had not tried access localhost:80
I have no tried localhost:80 and been presented with 'Apache2 Ubuntu Default Page'.
Still no sign of an 'ambar' page
@sochix commented on GitHub (Nov 16, 2017):
please, run
docker vesionanddocker-compose version. Paste the results here@uladzimir-shelhunou commented on GitHub (Dec 1, 2017):
The same issue with docker swarm, some services do not start with this error:
Used images:
mesosphere/mesos-master:1.4.0
mesosphere/mesos-slave:1.4.0
@sochix commented on GitHub (Dec 6, 2017):
@vvsh I'm curious why you use these images?
@sochix commented on GitHub (Jun 8, 2018):
No answer from Issue Opener