# The "Failed to install release agent" bug is back

**URL:** <https://forums.balena.io/t/the-failed-to-install-release-agent-bug-is-back/1810>\
**Category:** Product support\
**Created:** [September 7, 2017, 1:20pm UTC](https://forums.balena.io/t/the-failed-to-install-release-agent-bug-is-back/1810 "2017-09-07T13:20:26Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![nghiant2710](https://avatars.discourse-cdn.com/v4/letter/n/90db22/32.png) [@nghiant2710](https://forums.balena.io/u/nghiant2710)\
**Post date:** [September 14, 2017, 10:09am UTC](https://forums.balena.io/t/the-failed-to-install-release-agent-bug-is-back/1810/9 "2017-09-14T10:09:19Z")

</div>

@Tristan107, you will see something like this

```auto
Cannot determine cgroup we are running in: No medium found
Failed to allocate manager object: No medium found
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.

```

if `/sys/fs/crgoup` is mounted, it’s related to these issues [https://github.com/systemd/systemd/issues/6477](https://github.com/systemd/systemd/issues/6477), [https://github.com/systemd/systemd/issues/6477](https://github.com/systemd/systemd/issues/6477). So for now, we won’t mount it in the base images and you can just ignore the “failed to install release agent” warning.

---

_[View the full topic](https://forums.balena.io/t/the-failed-to-install-release-agent-bug-is-back/1810)._
