-
Notifications
You must be signed in to change notification settings - Fork 68
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
Can not start-up the docker with the access-address, version 3.5.4 #5
Comments
As of version 3.3.26, you can solve this by adding the keyword 'virtual' after the access-address, if the access-address is not matching any physical address, for example:
|
no, the |
Which version are you using? |
3.5.4 |
Could you paste your configuration file? (you can mask IP addresses or anything that may be sensitive, just want to double check if everything is correct). |
Thanks for the input.
I am pretty sure that access-address in the fabric sub-stanza is not supported. The default there should be Also, under the service sub-stanza, you should have |
Any luck? We checked in the code and it really seems pretty straight forward that this error message message Can you try by adding IP address instead of the os.getenv and removing the access address from the fabric sub-stanza? Thanks. |
Just checked this with the recent version and it worked for me without a problem. |
Great! |
Update Dockerfile (added back python3-pip)
Hi
this is exactly the same as #1 , but with different aerospike version
any suggestions?
Thank you
The text was updated successfully, but these errors were encountered: