# Reusing Singularity VNC bc\_desktop configuration in apps

**URL:** https://discourse.openondemand.org/t/reusing-singularity-vnc-bc-desktop-configuration-in-apps/1882
**Category:** Get Help
**Tags:** question
**Created:** [January 25, 2022, 9:40am UTC](https://discourse.openondemand.org/t/reusing-singularity-vnc-bc-desktop-configuration-in-apps/1882 "2022-01-25T09:40:32Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![novosirj](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/novosirj/32/339_2.png) [@novosirj](https://discourse.openondemand.org/u/novosirj)
#### Post date: [February 22, 2022, 6:03pm UTC](https://discourse.openondemand.org/t/reusing-singularity-vnc-bc-desktop-configuration-in-apps/1882/6 "2022-02-22T18:03:37Z")

</div>

I think he’s talking about running this way:

> [@Mate Desktop in a Singularity container?](https://discourse.openondemand.org/t/mate-desktop-in-a-singularity-container/696/21):
>
> OK, I think I’ve solved this (finally sweat_smile). The first issue you’ve had, turns out the easiest thing to do is just to remove mate-power-manager. Users shouldn’t be able to restart the node anyhow which I think is that widget does. The second is something we’d [already seen apparently](https://github.com/OSC/ondemand-packaging/issues/71) and I just forgot about it. So, if you’ll notice in the definition file, there’s a different RPM url. I was not able to solve the issue with turbovnc 2.1.1. It says you need the openssl or gnutls librarie…

I’m here because I had a similar question – how to avoid having to duplicate that for every app (which honestly isn’t a huge burden, but it would be a nice-to-have).

---

_[View the full topic](https://discourse.openondemand.org/t/reusing-singularity-vnc-bc-desktop-configuration-in-apps/1882)._