-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] config.json returned as a folder #47
Comments
When I do this, I get the following error: > docker run --rm -it -v $basedir:/flywheel/v0/input -v $PWD/empty:/flywheel/v0/input/config.json -v $basedir:/flywheel/v0/output garikoitz/prfanalyze-vista
Could not read config.json! Or, if empty doesn't exist... > docker run --rm -it -v $basedir:/flywheel/v0/input -v empty:/flywheel/v0/input/config.json -v $basedir:/flywheel/v0/output garikoitz/prfanalyze-vista
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/docker/volumes/empty/_data\\\" to rootfs \\\"/var/lib/docker/overlay2/051177842c265dde728de807f82ec4d6e044bdd13fcd73b0b345d24512654901/merged\\\" at \\\"/var/lib/docker/overlay2/051177842c265dde728de807f82ec4d6e044bdd13fcd73b0b345d24512654901/merged/flywheel/v0/input/config.json\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type. Is there something in your |
No, it was an empty folder.
If I give the path, it writes it correctly. It is weird.
We updated the wiki, if you go to the home page, you can copy and paste
everything and everything works fine (even the adding the empty folder).
Can it be that this happened when I used empty: instead of $basedir/empty,
and the docker container requires to mount with an absolute path? Sorry,
not with a computer right now, I will be able to check with computer in
some minutes
…On Mon, Mar 30, 2020 at 1:24 PM Noah C. Benson ***@***.***> wrote:
When I do this, I get the following error:
> docker run --rm -it -v $basedir:/flywheel/v0/input -v $PWD/empty:/flywheel/v0/input/config.json -v $basedir:/flywheel/v0/output garikoitz/prfanalyze-vista
Could not read config.json!
Or, if empty doesn't exist...
> docker run --rm -it -v $basedir:/flywheel/v0/input -v empty:/flywheel/v0/input/config.json -v $basedir:/flywheel/v0/output garikoitz/prfanalyze-vista
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/docker/volumes/empty/_data\\\" to rootfs \\\"/var/lib/docker/overlay2/051177842c265dde728de807f82ec4d6e044bdd13fcd73b0b345d24512654901/merged\\\" at \\\"/var/lib/docker/overlay2/051177842c265dde728de807f82ec4d6e044bdd13fcd73b0b345d24512654901/merged/flywheel/v0/input/config.json\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
Is there something in your empty file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCZAVZ54ZDDPQ5W6AJNP6LRKD5W5ANCNFSM4LVV7AAQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running this code, it throws a folder instead of a file
docker run --rm -it \
The text was updated successfully, but these errors were encountered: