# Docker bootstrap failing with exit 137

**URL:** https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [4 april 2014 om 11:36 UTC](https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457 "2014-04-04T11:36:27Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ankur](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ankur/32/108565_2.png) [@ankur](https://meta.discourse.org/u/ankur)
#### Post date: [4 april 2014 om 11:36 UTC](https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457/1 "2014-04-04T11:36:27Z")

</div>

Hello,

I’ve been trying to install Discourse inside an Ubuntu Precise VM (running on VirtualBox) using [these instructions](https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md). The process fails while running `./launcher bootstrap app` with the following output:

```
/pups/lib/pups/exec_command.rb:85:in `spawn': cd /var/www/discourse && sudo -E -u discourse bundle install --deployment --verbose --without test --without development failed with return #<Process::Status: pid 257 exit 137> (RuntimeError)
    from /pups/lib/pups/exec_command.rb:55:in `block in run'
    from /pups/lib/pups/exec_command.rb:53:in `each'
    from /pups/lib/pups/exec_command.rb:53:in `run'
    from /pups/lib/pups/command.rb:6:in `run'
    from /pups/lib/pups/config.rb:85:in `block (2 levels) in run_commands'
    from /pups/lib/pups/config.rb:76:in `each'
    from /pups/lib/pups/config.rb:76:in `block in run_commands'
    from /pups/lib/pups/config.rb:75:in `each'
    from /pups/lib/pups/config.rb:75:in `run_commands'
    from /pups/lib/pups/config.rb:71:in `run'
    from /pups/lib/pups/cli.rb:31:in `run'
    from /pups/bin/pups:8:in `<main>'
3bc24de467160ae901711cf5009ff9afa1c9178c03bf95ff200a184f81793ad8
FAILED TO BOOTSTRAP

```

What could I be doing wrong? Is there any more information about my environment that I can give you to help you diagnose this issue?

EDIT: is there something that’s very specific to DigitalOcean in these instructions?

EDIT 2: I just tried the “advanced” guide, with the same result.

Thanks.

---

<div class="post-metadata">

### Author: ![trident](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trident/32/2078_2.png) [@trident](https://meta.discourse.org/u/trident)
#### Post date: [4 april 2014 om 13:45 UTC](https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457/2 "2014-04-04T13:45:21Z")

</div>

How much memory have you given your VM? It sounds like you’re running out of memory.

---

<div class="post-metadata">

### Author: ![ankur](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ankur/32/108565_2.png) [@ankur](https://meta.discourse.org/u/ankur)
#### Post date: [4 april 2014 om 14:41 UTC](https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457/3 "2014-04-04T14:41:44Z")

</div>

That did the trick. Thanks!

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [4 april 2014 om 16:12 UTC](https://meta.discourse.org/t/docker-bootstrap-failing-with-exit-137/14457/4 "2014-04-04T16:12:26Z")

</div>

> [@trident](#):
>
> It sounds like you’re running out of memory.

Ooh, didn’t know that exit code 137 meant the process was KILLed (here, by the `oom-killer`)! Learn something new 😃