You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2021/07/16 16:32:00 UTC

[jira] [Resolved] (SOLR-15545) Properly source run-initdb in docker commands

     [ https://issues.apache.org/jira/browse/SOLR-15545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Houston Putman resolved SOLR-15545.
-----------------------------------
    Fix Version/s: main (9.0)
       Resolution: Fixed

> Properly source run-initdb in docker commands
> ---------------------------------------------
>
>                 Key: SOLR-15545
>                 URL: https://issues.apache.org/jira/browse/SOLR-15545
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Docker
>    Affects Versions: main (9.0)
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>             Fix For: main (9.0)
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently in various docker commands, such as {{solr-precreate}}, {{solr-foreground}}, {{solr-create}} and {{solr-demo}}, {{run-initdb}} is run as a child process. This means that any environment variables that are exported in {{run-initdb}} are ignored after the child-process is complete. We instead need to go back to sourcing {{run-initdb}}, so that the environment variables are passed to {{solr-fg}}.
> This is not the case in the 8.x docker-solr docker images, just the unreleased 9.0 docker image so far.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org