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] chown solr:solr fails on Solr 3:6 service with custom data directory. #692

Closed
tylerssn opened this Issue Feb 7, 2018 · 9 comments

Comments

Projects
None yet
4 participants
@tylerssn
Copy link

tylerssn commented Feb 7, 2018

When using solr:3.6 type (referenced in plugins/lando-services/services/solr/solr.js:53 with a custom directory setting, the Solr service fails at plugins/lando-services/services/solr/solr.js:119 with a user does not exist error.

My Lando Config:

  solr:
    type: solr:3.6
    portforward: true
    config:
      conf: custom/lib/Apache/Solr/conf

Based on the owner of /opt/solr/example/solr/conf within the Solr service it looks like the owner should be www-data.

@tylerssn

This comment has been minimized.

Copy link
Author

tylerssn commented Feb 9, 2018

Temporary workaround:

  solr:
    type: solr:3.6
    portforward: true
    overrides:
      services:
        build: ${PWD}/dev/lando/services/solr
    extras:
      - 'chown -R www-data:www-data  /opt/solr/example/solr/conf'
# Extending Lando's preferred solr:3.6 image with RUN adduser solr

FROM actency/docker-solr:3.6
RUN adduser solr
@dustinleblanc

This comment has been minimized.

Copy link
Member

dustinleblanc commented Feb 17, 2018

Thanks for the extra info @tylerssn! Appreciate the solid bug report.

@tylerssn

This comment has been minimized.

Copy link
Author

tylerssn commented Feb 23, 2018

Anything to help. Love the service.

@pirog pirog added this to the 3.0.0-beta.41 milestone Apr 8, 2018

@pirog pirog self-assigned this Apr 8, 2018

@pirog pirog removed this from the 3.0.0-beta.41 milestone Apr 30, 2018

@zuernBernhard

This comment has been minimized.

Copy link

zuernBernhard commented Jul 9, 2018

@pirog what is missing to merge this ?

@dustinleblanc

This comment has been minimized.

Copy link
Member

dustinleblanc commented Jul 9, 2018

Considering this is an issue and not a PR...I'd guess...code is missing? 😆

@pirog

This comment has been minimized.

Copy link
Member

pirog commented Jul 10, 2018

yeah ditto on what @dustinleblanc said. there isnt any code to merge here so quite a lot is missing.

im guessing we will tackle this (unless someone else does first) post rc1 because we will be better equipped re: testing infrastructure

@tylerssn

This comment has been minimized.

Copy link
Author

tylerssn commented Jul 16, 2018

@zuernBernhard - if you simply need to get this to a working state, see #692 (comment)

@pirog pirog removed solr labels Jan 31, 2019

@pirog pirog added this to the 3.0.0-rc.3 milestone Feb 1, 2019

@pirog

This comment has been minimized.

Copy link
Member

pirog commented Feb 1, 2019

This is something we should be able to test and fix pretty easily now!

pirog added a commit that referenced this issue Feb 3, 2019

@pirog

This comment has been minimized.

Copy link
Member

pirog commented Feb 4, 2019

Alright! SOLR 3.6! uhhhh right? :/

@pirog pirog closed this Feb 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment