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
Need to have msitools installed on the builder docker images for osquerybeat packaging in order to be able to extract osquueryd.exe binary from the official .msi windows distribution package.
Describe a specific use case for the enhancement or feature:
The official signed osquery distro for windows is only available as .MSI package for downloads.
Previously we shipped .MSI inside of osquerybeat bundle for windows and extracted the osqueryd.exe file using msiexec, the very first time osquerybeat was started.
There was a error observed in the logs and reported by one of the customers while running msiexec during osquerybeat installation. We could not reproduce that error and there are multiple potential causes for that specific error message documented by Microsoft.
The solution was to install msitools on the debian docker image during osquerybeat build/packaging for windows and extract the osqueryd.exe binary during osquerybeat build process. Ideally we would like to have these tools baked in into the builder docker image in order to avoid installing them on each build/package request.
Opening this tracker in response to the PR's review comment: #29801 (comment)
The text was updated successfully, but these errors were encountered:
Describe the enhancement:
Need to have msitools installed on the builder docker images for osquerybeat packaging in order to be able to extract osquueryd.exe binary from the official .msi windows distribution package.
Describe a specific use case for the enhancement or feature:
The official signed osquery distro for windows is only available as .MSI package for downloads.
Previously we shipped .MSI inside of osquerybeat bundle for windows and extracted the osqueryd.exe file using msiexec, the very first time osquerybeat was started.
There was a error observed in the logs and reported by one of the customers while running msiexec during osquerybeat installation. We could not reproduce that error and there are multiple potential causes for that specific error message documented by Microsoft.
The solution was to install msitools on the debian docker image during osquerybeat build/packaging for windows and extract the osqueryd.exe binary during osquerybeat build process. Ideally we would like to have these tools baked in into the builder docker image in order to avoid installing them on each build/package request.
Opening this tracker in response to the PR's review comment:
#29801 (comment)
The text was updated successfully, but these errors were encountered: