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
When building the session-manager-plugin binary from source code using Docker, the resulting binary exits unexpectedly when used with the AWS-StartPortForwardingSessionToRemoteHost document.
Steps to reproduce
Clone repo (reproduces on 1.2.398.0 and previous versions)
In 2 to 5 minutes, the session will end unexpectedly. (Idle session timeout: 20m, Maximum session duration: 60m are set in the session manager settings in AWS console)
Considerations
The session-manager-plugin binary downloaded from the link provided in the installation manual normally works in the same scenario. Looks like the build process used for the installation packages differs from what's described in the readme. Another piece of evidence for this is that the VERSION file in the repository contains 1.2.0.0 while the downloaded package contains the correct version (1.2.398.0 in my case).
It would be great if properly built binaries were released along with the source code for each release.
Or maybe my way of using the build artifacts is wrong?
The text was updated successfully, but these errors were encountered:
I ended up using version 1.2.295.0 in my project (https://github.com/basti-app/basti). The build result is fine for the version. It would be great to be able to upgrade to newer versions.
Summary
When building the
session-manager-plugin
binary from source code using Docker, the resulting binary exits unexpectedly when used with theAWS-StartPortForwardingSessionToRemoteHost
document.Steps to reproduce
docker build -t session-manager-plugin-image .
docker run -it --rm --name session-manager-plugin -v
pwd:/session-manager-plugin session-manager-plugin-image make release
bin/darwing_amd64_plugin/session-manager-plugin
for MacOS) to the installation folder (/usr/local/bin/
for MacOS)Considerations
The session-manager-plugin binary downloaded from the link provided in the installation manual normally works in the same scenario. Looks like the build process used for the installation packages differs from what's described in the readme. Another piece of evidence for this is that the
VERSION
file in the repository contains1.2.0.0
while the downloaded package contains the correct version (1.2.398.0
in my case).It would be great if properly built binaries were released along with the source code for each release.
Or maybe my way of using the build artifacts is wrong?
The text was updated successfully, but these errors were encountered: