Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure with no output when running Sleeper CLI without images #3448

Open
patchwork01 opened this issue Oct 10, 2024 · 1 comment
Open

Failure with no output when running Sleeper CLI without images #3448

patchwork01 opened this issue Oct 10, 2024 · 1 comment
Labels
bug Something isn't working under-discussion

Comments

@patchwork01
Copy link
Collaborator

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

  1. Install Sleeper CLI
  2. Run docker system prune -af
  3. Run sleeper environment
  4. See the command exits without starting a Docker container or giving any output

Expected behaviour

We should either see a failure explaining that the image is missing, or the image should be automatically downloaded.

@rtjd6554
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working under-discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants