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
Fix for issue was the remove the --quiet flag from the cli to allow for full output to be returned allowing the docker to react correctly when interacting with components that had been shut down.
This output however was too excessive in impact for just the fix so another solution will need to be looked at.
Other flags for the docker were investigated during the ticket but none looked to behave in similar fashion.
Behaviour of prune action was also looked at for understanding and seeing if that had any impact on the behaviour presented in the issue, however nothing found seemed to differ from the expected behaviour for docker.
Possible route for resolution could lie within how the flow of the docker commands are executed after the build, however investigation of such would be potentially large and beyond scope for just this bug.
Present recommendation is to move issue to the backlog until further discussion of issue is available.
Description
If you delete the Docker images for the Sleeper CLI, when you run a CLI command that runs a Docker image, it fails without any output.
Steps to reproduce
docker system prune -af
sleeper environment
Expected behaviour
We should either see a failure explaining that the image is missing, or the image should be automatically downloaded.
The text was updated successfully, but these errors were encountered: