# Get systemd installed in a Balena image (genericx86-64-ext-debian-node:latest-bullseye)

**URL:** <https://forums.balena.io/t/get-systemd-installed-in-a-balena-image-genericx86-64-ext-debian-node-latest-bullseye/365457>\
**Category:** balenaEngine\
**Tags:** support, docker\
**Created:** [November 16, 2022, 6:33pm UTC](https://forums.balena.io/t/get-systemd-installed-in-a-balena-image-genericx86-64-ext-debian-node-latest-bullseye/365457 "2022-11-16T18:33:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![damianruiz](https://avatars.discourse-cdn.com/v4/letter/d/f05b48/32.png) [@damianruiz](https://forums.balena.io/u/damianruiz)\
**Post date:** [November 16, 2022, 6:33pm UTC](https://forums.balena.io/t/get-systemd-installed-in-a-balena-image-genericx86-64-ext-debian-node-latest-bullseye/365457/1 "2022-11-16T18:33:25Z")

</div>

I upgraded the balena base image from `genericx86-64-ext-debian-node:12-buster` to `genericx86-64-ext-debian-node:latest-bullseye` and the systemd config stopped working.  
The current configuration is the one here: [base-images/examples/INITSYSTEM/systemd/systemd.v230 at master · balena-io-library/base-images · GitHub](https://github.com/balena-io-library/base-images/tree/master/examples/INITSYSTEM/systemd/systemd.v230)

I am running some services of my application, which are not starting

When I run `systemctl status default.target` I get the message: `default.target is masked.`

I am getting the following error in the console

 ![Captura de Pantalla 2022-11-14 a la(s) 14.04.00](https://global.discourse-cdn.com/balena/original/2X/4/45f06fb999f4d3263f5355618845f9c1ec43b998.png)

---

<div class="post-metadata">

**Author:** ![rahul-thakoor](https://avatars.discourse-cdn.com/v4/letter/r/9de053/32.png) [@rahul-thakoor](https://forums.balena.io/u/rahul-thakoor)\
**Post date:** [December 27, 2022, 11:41am UTC](https://forums.balena.io/t/get-systemd-installed-in-a-balena-image-genericx86-64-ext-debian-node-latest-bullseye/365457/2 "2022-12-27T11:41:34Z")

</div>

Hi @damianruiz

Welcome to the forums!

Are you still running into this issue?

looks like a bump in systemd version might cause that?

Can you please share your Dockerfile? This will help us confirm how you are installing the service in the container and the services you are masking

Thanks