You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to install wazuh on linux Virtual PC which is behind a http proxy. "docker-compose -f generate-indexer-certs.yml run --rm generator " this command doesn't work as it throws error
The tool to create the certificates does not exist in any bucket. Then I entered the docker container and tried to run random curl command and it didn't work which means the env variables were not set properly. SO I manually exported env variables inside docker container then ran entry point.sh script to complete the execution. Still it throws the same error .
Thanks
Celine
The text was updated successfully, but these errors were encountered:
because they wrote 5.0.0 in the docker compose file from memory, (but version 0.0.0.2) whereas the latest image 0.0.2 doesn't come even if you fix generate-indexer-certs.yml,
I am trying to install wazuh on linux Virtual PC which is behind a http proxy. "docker-compose -f generate-indexer-certs.yml run --rm generator " this command doesn't work as it throws error
The tool to create the certificates does not exist in any bucket. Then I entered the docker container and tried to run random curl command and it didn't work which means the env variables were not set properly. SO I manually exported env variables inside docker container then ran entry point.sh script to complete the execution. Still it throws the same error .
Hi
I am trying to install wazuh on linux Virtual PC which is behind a http proxy. "docker-compose -f generate-indexer-certs.yml run --rm generator " this command doesn't work as it throws error
The tool to create the certificates does not exist in any bucket. Then I entered the docker container and tried to run random curl command and it didn't work which means the env variables were not set properly. SO I manually exported env variables inside docker container then ran entry point.sh script to complete the execution. Still it throws the same error .
Thanks
Celine
The text was updated successfully, but these errors were encountered: