EngineFailure EACCESS permission denied (X)Ubuntu 14.04

[bdunn313]

I'm getting a similar result to issue #1 (engine failure), however I get a bit more robust error message:

error: (CC::Analyzer::Engine::EngineFailure) engine eslint failed with status 1 and stderr "fs.js:761
return binding.readdir(pathModule._makeLong(path));
    Error: EACCES, permission denied '/code'
        at Error (native)
        at Object.fs.readdirSync (fs.js:761:18)
        at traverse (/usr/src/app/node_modules/eslint/lib/util/traverse.js:41:12)    
        at walk (/usr/src/app/node_modules/eslint/lib/util/traverse.js:83:9)    
        at /usr/src/app/node_modules/eslint/lib/util/traverse.js:102:9
        at Array.forEach (native)
        at traverse (/usr/src/app/node_modules/eslint/lib/util/traverse.js:101:11)
        at CLIEngine.executeOnFiles (/usr/src/app/node_modules/eslint/lib/cli-engine.js:323:9)
        at Object.<anonymous> (/usr/src/app/bin/eslint:42:18)
        at Module._compile (module.js:460:26)"

(reformatted for easier reading)

I do not have any directory /code within my project, so I'm assuming this is within the docker container.

Here's my .codeclimate.yml file:

---
engines:
  eslint:
    enabled: true
  csslint:
    enabled: true
  phpcodesniffer:
    enabled: true
ratings:
  paths:
  - "**.php"
  - "**.js"
  - "**.jsx"
  - "**.css"
exclude_paths:
- config/**/*
- spec/**/*
- tests/**/*
- node_modules/**/*
- vendor/**/*
- resources/views/**/*
- features/**/*
- database/**/*
- bootstrap/**/*
- public/**/*
- storage/**/*
- docs/**/*
- .idea/**/*

Unforunately I cannot provide source code for the project as it is a private codebase, but it is more-or-less the structure of a Laravel 5.0 codebase (PHP).

Please let me know if I can help debug this issue further, just wanted to report it because I know this is a young project! Thanks for releasing the engine!

[sublimecoder]

I'm getting a similar error when trying to set it up with a rails app.

Starting analysis
Running rubocop: Done!
Running eslint: Done!
error: (CC::Analyzer::Engine::EngineFailure) engine eslint failed with status 1 and stderr "
fs.js:0\n(function (exports, require, module, __filename, __dirname) { // Copyright Joy 
          Error: ENOENT, no such file or directory '/code/public/sitemap.xml'\n    
       at Error (native)\n    
           at Object.fs.statSync (fs.js:797:18)\n    
       at /usr/src/app/node_modules/eslint/lib/util/traverse.js:50:27\n    
       at Array.forEach (native)\n    
       at traverse (/usr/src/app/node_modules/eslint/lib/util/traverse.js:41:54)\n    
       at /usr/src/app/node_modules/eslint/lib/util/traverse.js:63:17\n    
       at Array.forEach (native)\n    
       at traverse (/usr/src/app/node_modules/eslint/lib/util/traverse.js:41:54)\n    
       at walk (/usr/src/app/node_modules/eslint/lib/util/traverse.js:83:9)\n    
       at /usr/src/app/node_modules/eslint/lib/util/traverse.js:102:9\n"

[pbrisbin]

@bdunn313 the current working directory (the directory containing your source files) is mapped to /code within the container. So your error is indicating that the docker container cannot access your current directory. Do you have restricted permissions on the source directory itself?

@sublimecoder this error is saying public/sitemap.xml does not exist. Does it?

[bdunn313]

@pbrisbin permissions may be the culprit - the project directory is a subfolder of my home folder (xubuntu 14.04) so this means the user and group is myself. However, docker runs as the docker user (per setup instructions for docker).

As soon as I can, I am going to try and add docker to a shared group that should give it access to my project folder and report back whether or not that fixed the issue.

Thanks for the insight

EDIT: Fixing permissions does seem to have done the trick. I did not have a permissive working directory, specifically I only had read/write access set up for my personal users , not even my user group.

Sorry for the poor investigation on my part - I was a bit too quick to report an issue. Thank you for taking the time to help me address this. I did run into another issue, but it does not seem related so I will open a new one once I've exhausted my own troubleshooting abilities.