mitchlloyd commented on pull request #10386:
URL: https://github.com/apache/druid/pull/10386#issuecomment-698009601


   I probably should have specifically called out that I have the `DOCKER_IP` 
environment variable set to `127.0.0.1` per the instructions since that seems 
like a likely culprit.
   
   I took another shot at this today. I ran `docker login` to make sure I was 
logged into Dockerhub. I also disabled some maven configuration that I have 
that pulls packages through an Artifactory proxy repository in case that 
mattered.
   
   As a demonstration I also put this env var in the command and still saw 
`Could not set docker host IP - integration tests can not run`:
   
   ```bash
   DOCKER_IP=127.0.0.1 mvn verify -pl integration-tests \
      -P integration-tests \
     -Dgroups=s3-deep-storage \
     -Doverride.config.path=s3-creds-override \
     -Ddruid.test.config.streamEndpoint=kinesis.us-west-2.amazonaws.com \
     -Ddruid.test.config.cloudBucket=<MY-BUCKET-NAME> \
     -Ddruid.test.config.cloudPath=s3-tests/
   ```
   
   So then I honed in on this command which seemed to be not working and giving 
me the error.
   
   ```
   dscacheutil -q host -a name "$(HOSTNAME)" | perl -nle '/ip_address: (.*)/ && 
print $1' | tail -n1
   ```
   
   I don't have a HOSTNAME env var so I tried setting that to `localhost`. Then 
I needed to remove some parenthesis around HOSTNAME to get that command to 
return a value:
   
    ```
   > dscacheutil -q host -a name "$HOSTNAME" | perl -nle '/ip_address: (.*)/ && 
print $1' | tail -n1
   > 127.0.0.1
   ```
   
   With that change I see a lot more RSA keys being generated:
   
   ```
   Generating RSA private key, 1024 bit long modulus
   ```
   
   And now I'm able to run the tests!
   
   From here it looks like to make sure all of my config is right but at least 
I have the tests running 👍 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to