Skip to content
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

docker-compose build failed #6809

Closed
2 tasks
tateisu opened this issue Mar 17, 2018 · 5 comments
Closed
2 tasks

docker-compose build failed #6809

tateisu opened this issue Mar 17, 2018 · 5 comments

Comments

@tateisu
Copy link
Contributor

tateisu commented Mar 17, 2018

[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "node-gyp@3.6.2" with binaries:
      - node-gyp
[6/6] Cleaning modules...
error An unexpected error occurred: "ENOENT: no such file or directory, open '/usr/local/share/.config/yarn/global/.yarnclean'".
info If you think this is a bug, please open a bug report with the information provided in "/usr/local/share/.config/yarn/global/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
ERROR: Service 'sidekiq_push' failed to build: The command '/bin/sh -c bundle config build.nokogiri --with-iconv-lib=/usr/local/lib --with-iconv-include=/usr/local/include  && bundle install -j$(getconf _NPROCESSORS_ONLN) --deployment --without test development  && yarn --pure-lockfile  && yarn cache clean' returned a non-zero code: 1

  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
  • This bug happens on a tagged release and not on master (If you're a user, don't worry about this).
@Gargron
Copy link
Member

Gargron commented Mar 17, 2018

Looking into it right now.

@tateisu
Copy link
Contributor Author

tateisu commented Mar 17, 2018

I've tryed on 2 instance from tags/v2.3.2rc1 , both failed.

@Moskito99
Copy link

Yepp! Same for me. Does not build....

@Gargron
Copy link
Member

Gargron commented Mar 17, 2018

The cause is unclear but I'm testing a fix right now

Gargron added a commit that referenced this issue Mar 17, 2018
Fix #6809

I don't know why, either
Gargron added a commit that referenced this issue Mar 17, 2018
@akihikodaki
Copy link
Contributor

I investigated this issue and found yarn changes config.cwd to /usr/local/share/.config/yarn/global/.yarnclean in init method of PackageInstallScripts if npm is not present. However I'm still not sure why.
git is added to the image but apparently it is not related.

smorimoto pushed a commit to kibousoft/mastodon that referenced this issue Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants