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 starting VBM vault pipeline, this error occurs:
Pipeline Error: Error: Container websocket server timeout exceeded
After waiting 10-15 mins, restarted the pipelines and then run fine.
Random info.:
For https://github.com/trendscenter/coinstac-msr-fsl
I was running coinstac-sim on my mac.
I edited a image and committed changes to overwrite the image.
I ran the sim again and noticed this error:
Simulator run failed!sage: Pipeline Error: Error: Container websocket server timeout exceeded, level: error }
I tried to get into the image using 'docker run -it coinstacteam/msr-fsl' and it said:
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
I have no clue if this is relevant for ec2 vault instances at all, but just coz I noticed a similar error with sim, I wanted to report it here if it helps.
The text was updated successfully, but these errors were encountered:
When starting VBM vault pipeline, this error occurs:
Pipeline Error: Error: Container websocket server timeout exceeded
After waiting 10-15 mins, restarted the pipelines and then run fine.
Random info.:
For https://github.com/trendscenter/coinstac-msr-fsl
I was running coinstac-sim on my mac.
I edited a image and committed changes to overwrite the image.
I ran the sim again and noticed this error:
Simulator run failed!sage: Pipeline Error: Error: Container websocket server timeout exceeded, level: error }
I tried to get into the image using 'docker run -it coinstacteam/msr-fsl' and it said:
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
I have no clue if this is relevant for ec2 vault instances at all, but just coz I noticed a similar error with sim, I wanted to report it here if it helps.
The text was updated successfully, but these errors were encountered: