Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah. My sprites never idled inspite of having nothing running in them and had to be destroyed. Ideally there should be two settings

1. A timeout after the last console session is exited 2. Force idle using the CLI



Just tried it again. Creation took a very long time, then errored.

    $ sprite version
    sprite version v0.0.1-rc30

    $ sprite create quk

     Error creating sprite: failed to create sprite: Post "https://api.sprites.dev/v1/sprites": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

But despite the error, the sprite was apparently created, and it runs continuously.

    $ sprite ls
    Sprites in organization <redacted>:

    ┌────┬───────┬────────┐
    │NAME│STATUS │CREATED │
    ├────┼───────┼────────┤
    │quk │running│14m ago │
    └────┴───────┴────────┘

    Total: 1 sprite(s)


Get a console in your sprite. Run “screen”. Run a loop in there : while date; do sleep 1; done. Detach screen and exit the session. Wait a few minutes and go back into the sprite. Reattach screen. You’ll see a gap in the timestamps.

They do suspend even when they say they are “running”.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: