Nicolas Vuillamy

@schorlton why not just defining a local .pylintrc in your repo to disable import error issue ?

@schorlton @wenzeslaus MegaLinter wants to address any kind of projet in any language :) About imports... if you want to let the rule active, maybe you could install python dependencies...

So you mean a flavor python + C-like languages ? :)

I already tried to build MegaLinter without user root user... and I failed , but if you find a way, that can be nice :)

The dockerfile is full of references to root folder, so I think default user is root yes https://github.com/megalinter/megalinter/blob/2dac18c05aee04d0d2282f52fb724648e61fca64/Dockerfile#L247

@Kurt-von-Laven i struggle since yesterday with new git patch... if you find a solution you're my hero :)

It's probably possible :) https://medium.com/swlh/using-github-actions-to-build-arm-based-docker-images-413a8d498ee But will take some time if I have to do it myself because of my little available time these days ^^ We could have "mirror"...

Thank a lot for your analysis :) About not compliant linters, we could eventually flag them in descriptors so they are simply not added within arm64 images Story to be...

@estahn do you still have the issue ?

Note: some people succeed, but maybe they had to tweak the workflow https://github.com/search?q=%5BApply+MegaLinter+fixes%5D&type=commits It also works better with PAT defined, else after the new commit, the Github Actions Workflows are...