Upgrading the Ulteo Environment - Lucid

[Stuart England]

Hey guys, not sure what its correct name is but is it possible to update the chroot environment from Lucid to something newer. Google have dropped support for Lucid which is causing me issues.

Better yet, is there a way to have a normal ubuntu server ({14.04 etc) serve up applications to ulteo rather than this chroot environment

thanks

Stuart

[Christophe Bourcier]

Hi Stuart,

You can create an OVD subsystem in any of the distributions for which OVD has been packaged. The last version of Ubuntu supported is Precise Pangolin. See http://archive.ulteo.com/ovd/4.0.1/ubuntu/pool

The idea is to create a chroot of your favourite supported distribution (using debootstrap), add the Ulteo repository to apt sources list, and add the specific packages needed for a subsystem:
apt-get install ulteo-ovd-desktop ulteo-ovd-slaveserver ulteo-ovd-slaveserver-role-aps ulteo-ovd-slaveserver-role-fs uxda-server ulteo-ovd-externalapps-client ulteo-ovd-integrated-launcher ulteo-xfce4-restricted-menu-plugin libovd-xclient-area apache2 samba

You can try to install these packages in the main environment of your server instead of a chroot one. But at your own risk.

Christophe

[Vantz Stockwell]

Christophe,

I followed your directions however instead of using a chroot environment I'm using Docker for quicker testing... with Precise Pangolin 12.04 and OVD 4.0.2 however when I try to start Samba I get a launch error have you used this setup before?

[Christophe Bourcier]

I have used this setup to create a 64-bit Debian Squeeze subsystem called from a Debian Wheezy server. For all the information, see http://lides.fr/cms/how-to-create-your-own-ovd-subsystem

For samba, I had to create a link from smbd to samba, so that it can be started by /etc/init.d/ulteo-ovd-subsystem:

cd /etc/init.d
ln -s samba smbd

But I still have the login bug described here https://groups.google.com/forum/#!topic/ulteo-ovd-community-support/gmBqqkHOrRU
I have to disable the fs role to be able to login. I have this bug also on a fresh OVD installation with the original subsystem.

[Vantz Stockwell]

Christophe thanks for your help I have achieved a new chroot on our production environment. However I was wondering have you tried or succeeded upgrading Guacamole or Tomcat yet?

[Mico]

Well, Precise seems to be having issues on a restart.  Everything works good until I restart the server...

root@ulteoapp1:~# /etc/init.d/ulteo-ovd-subsystem restart

 * Stopping Ulteo OVD SlaveServer                                                                                               * not running

 * Stopping web server apache2                                                                                                 apache2: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName

 ... waiting .                                                                                                          [ OK ]

smbd stop/waiting

 * Stopping xrdp-printerd                                                                                               [ OK ]

 * Stopping xrdp-sesman                                                                                                 [ OK ]

 * Stopping xrdp                                                                                                        [ OK ]

 * Stopping xrdp-logd                                                                                                   [ OK ]

cups stop/waiting

umount: /: not mounted

umount: /dev: not mounted

umount: /: not mounted

umount: /: not mounted

umount: /dev: not mounted

umount: /: not mounted

cups start/running, process 1084

 * Starting xrdp-logd                                                                                                   [ OK ]

 * Starting xrdp                                                                                                        [ OK ]

 * Starting xrdp-sesman                                                                                                 [ OK ]

 * Starting xrdp-printerd                                                                                               [ OK ]

smbd start/running, process 1170

 * Starting web server apache2                                                                                                 apache2: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName

                                                                                                                        [ OK ]

 * Starting Ulteo OVD SlaveServer                                                                                       [fail]

 * Re-starting Ulteo OVD subsystem                                                                                      [ OK ]

root@ulteoapp1:~# uchroot

bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)

root@ulteoapp1:/# /etc/init.d/ulteo-ovd-slaveserver

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)

 * Usage: /etc/init.d/ulteo-ovd-slaveserver {start|stop|force-stop|force-reload|restart}

root@ulteoapp1:/# /etc/init.d/ulteo-ovd-slaveserver start

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)

 * Starting Ulteo OVD SlaveServer                                                                                       [fail]

root@ulteoapp1:/# ulteo-ovd-slaveserver

2014-09-03 23:37:29,580 [INFO]: [1307] SlaveServer stop

2014-09-03 23:37:29,580 [INFO]: [1307] FileServer role::stop

2014-09-03 23:37:29,704 [ERROR]: [1307] groupMember KeyError: 'getgrnam(): name not found: None'

2014-09-03 23:37:29,705 [WARNING]: [1307] FSBackend is already stopped

2014-09-03 23:37:29,705 [INFO]: [1307] Role FileServer stopped

2014-09-03 23:37:29,705 [INFO]: [1307] SlaveServer stopped

Traceback (most recent call last):

  File "/usr/bin/ulteo-ovd-slaveserver", line 184, in <module>

    code, msg = main(None, config_file, pid_file)

  File "/usr/bin/ulteo-ovd-slaveserver", line 81, in main

    if not server.load_roles():

  File "/usr/lib/python2.7/dist-packages/ovd/SlaveServer.py", line 80, in load_roles

    role_instance = Role.Role(self)

  File "/usr/lib/python2.7/dist-packages/ovd/Role/ApplicationServer/Role.py", line 62, in __init__

    self.sessions_spooler = MPQueue.Queue()

  File "/usr/lib/python2.7/dist-packages/ovd/Role/ApplicationServer/MPQueue.py", line 70, in __init__

    self._rlock = Lock()

  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in __init__

    SemLock.__init__(self, SEMAPHORE, 1, 1)

  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__

    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)

OSError: [Errno 38] Function not implemented

root@ulteoapp1:/#

On Tuesday, September 2, 2014 11:40:33 AM UTC-5, Mico wrote:

I reinstalled the ulteo-ovd-subsystem on the application server and it appears to be working now.  This might have been caused due to different version of app servers running?

On Tuesday, September 2, 2014 10:00:18 AM UTC-5, Mico wrote:

Hi Christophe,

I'm having an issue with the File Server role with this subsystem.  I followed your instructions and successfully created a subsystem based upon Ubuntu 12.04 Precise Release.  It works fine as an application server, however, it fails to create the user profile when a user attempts to login to the server.  Here is the log:

Sep 2 09:46:51 - 131.230.133.204 - INFO - No webapp published for User "<LOGIN_UID_IS_HERE>"

Sep 2 09:46:51 - 131.230.133.204 - INFO - (client/start) Creating new session for <LOGIN_UID_IS_HERE> (14096692112EWlV)

Sep 2 09:46:52 - 131.230.133.204 - ERROR - SessionManagement::prepareFSAccess - Cannot enable FS access for User 'SIU853320867' on Server '8.8.8.8', aborting

Sep 2 09:47:03 - 131.230.133.204 - INFO - Session start : '14096692112EWlV'

I'm able to disable the FS role on the application server and utilize a baseline Lucid FS.  I tried it with your debian subsystem on an Ubuntu Precise host as well and the FS role appears to not work there as well.  I'm curious if you know the cause of this issue?  Thanks for all your help.

[Mico]

Well, I figure out my issue:

I must have messed up on this step:

rm -rf /dev/shm
mkdir /dev/shm
chmod 1777 /dev/shm

because, /opt/ulteo/dev/shm was still linking to /run/shm.  Looks like your installations are perfect.  Sorry for the confusion.

[Mico]

I was able to run the following command outside of chroot to startup the service:  Debating the effects of running this outside of chroot might be the only solution though unless anyone knows how to make RegularUnionFS run inside the chroot..

root@ulteoapp1:~# /opt/ulteo/usr/sbin/RegularUnionFS /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs.real /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs -o user=root -o fsconfig=/opt/ulteo/etc/ulteo/rufs/FSBackend.conf -d

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS mount point is /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS source path is /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs.real

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Switching to user root

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Parsing configuration...

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'umask=007' to section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'union=real' to section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'pidFile=/tmp/FSBackend.pid' to section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'sharesList="/etc/ulteo/rufs/shares.conf"' to section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'sharesQuotaGrace=10K' to section 'main'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'level=INFO' to section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'program=RegularUnionFS' to section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'enableDevelOutput=true' to section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'enableStdOutput=true' to section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'outputFilename="/tmp/FSBackend.log"' to section 'log'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding section 'real'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'path=""' to section 'real'

[2014:09:05-01:59:42] [DEBUG ] RegularUnionFS Adding key 'accept=""' to section 'real'

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:489] Configuration dump:

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:504] mounted path: /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:507]   shares files /etc/ulteo/rufs/shares.conf

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:529]  unionized path: /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs.real/

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:535]   accept symlink: false

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [configuration_dump:536]   delete on end: false

[2014:09:05-01:59:42] [WARN  ] RegularUnionFS [shares_reload:149] The share list file '/etc/ulteo/rufs/shares.conf' do not exist

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [shares_dump:188] Shares dump

fuse: warning: library too old, some operations may not not work

FUSE library version: 2.8.6

nullpath_ok: 0

unique: 1, opcode: INIT (26), nodeid: 0, insize: 56

INIT: 7.17

flags=0x0000047b

max_readahead=0x00020000

[2014:09:05-01:59:42] [INFO  ] RegularUnionFS [rufs_init:897] rufs inited

   INIT: 7.12

   flags=0x00000011

   max_readahead=0x00020000

   max_write=0x00020000

   unique: 1, success, outsize: 40

On Thursday, September 4, 2014 2:24:06 AM UTC-5, Mico wrote:

Actually, it appears Ubuntu precise forces /opt/ulteo/dev/sdh to link to /run/shm every startup

I ended up modifying the following file to make it mount properly so slaveserver starts on the app server at restart for ubuntu x64 precise app server:

#On the application server edit:

vi /etc/init.d/ulteo-ovd-subsystem

do_start() {

    [ -d "$CHROOTDIR" ] || return 1

    #Hack to fix ubuntu precise linking /opt/ulteo/dev/shm

    rm -rf /opt/ulteo/dev/shm

    mkdir /opt/ulteo/dev/shm

    chmod 1777 /opt/ulteo/dev/shm

[Mico]

Well, a person can probably add this command to /etc/init.d/ulteo-ovd-subsystem

do_start() {

    [ -d "$CHROOTDIR" ] || return 1

    #Hack to fix ubuntu precise linking /opt/ulteo/dev/shm

    rm -rf /opt/ulteo/dev/shm

    mkdir /opt/ulteo/dev/shm

    chmod 1777 /opt/ulteo/dev/shm

    #Hack to make RegularUnionFS work with chroot on Ubuntu Precise

    /opt/ulteo/usr/sbin/RegularUnionFS /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs.real /opt/ulteo/var/lib/ulteo/ovd/slaveserver/fs -o user=root -o fsconfig=/opt/ulteo/etc/ulteo/rufs/FSBackend.conf

    cp /tmp/FSBackend.log /opt/ulteo/tmp/FSBackend.log

[Mico]

Well, it needs a bit more work.. getting another error:

Failed to add entry for the share 'p_1409903039M7wgj' OSError: [Errno 3] No such process

I need to rework it so the execute permissions and everything are the same.

[Christophe Bourcier]

Hi Mico,

Thank you for your comments and for investigating this issue. I haven't managed to solve it so far.

Christophe

[Christophe Bourcier]

Good news everyone! I finally got it working!

You were right that fuse was the problem.

But you don't need to add a command line to call RegularUnionFS, since it is already done in the chroot by /usr/share/pyshared/ovd/Role/FileServer/FSBackend.py

What was missing was a special file /dev/fuse with the good access rights.

I am not sure what is the proper way to do it in a chroot though.

Method 1
=======

In the chroot:
touch /dev/fuse

In the host:
mount --bind /dev/fuse /opt/ulteo/dev/fuse

Unfortunately, the groups fuse in the host and in the chroot don't have the same gid. As a result, /dev/fuse is owned by the group lpadmin.

So I had to chmod o+rw /dev/fuse to give full read/write acces, which is not very safe.

This mount command can be added in /etc/init.d/ulteo-ovd-subsystem do_start()
And the corresponding umount in do_stop()

Method 2
=======

Warning: if you have tried method 1, first do: umount /opt/ulteo/dev/fuse

In the host:
rsync -a /dev/fuse /opt/ulteo/dev/fuse

In the chroot:
chown root.fuse /dev/fuse

With both methods, I am able to login with the FS role on, and to have persistent files between sessions.

Any advice on what is the best way to create /dev/fuse in a chroot?

Christophe

[Mico]

Christophe,

Your solution works for me as well for me the Ubuntu Precise x64 build.  I actually had an error in my sessionmanager that was causing mine to not work but, I'm glad you tested this you found a much cleaner way of sharing the missing /dev/fuse across the chroot.

For what it is worth,

The issue is the fuse kernel module is not loading in chroot's kernel.  This is why your having the bind the /dev/fuse to /opt/ulteo/dev/fuse.

Kernel modules are located in /lib/modules/3.2.0-60-virtual/

I'm debating if it might be better to load these modules into the chroot's kernel and allow the program to do the fuse operation between the directories, rather than on the host side.  This would prevent world read/write on the app server.

We should be looking to implement something like:

# modprobe fuse

(after we get the required lib's in the chroot) unless we can find a better way of removing world read/write.

[Mico]

Chritophe,

I was actually looking into this on the ovd demo appliance.  /dev/fuse is world rw.  I think it might be required since all users need to use it to both read and write.  So your solution is probably good enough,.

[Mico]

Attaching my completed documentation for x64 subsystem for Ubuntu.  Feel free to use on your website.

[Mico]

Chritophe,

I examined the installed chroot of lucid today to see exactly what they have setup for security in regards to /dev/fuse.

Anyway, I think placing the following into /etc/init.d/ulteo_ovd_subsystem will result in just read and write for root and group fuse for the device.

place under on_startup:

#Hack to fix fuse module not loading in chroot

	touch /opt/ulteo/dev/fuse

	mount --bind /dev/fuse /opt/ulteo/dev/fuse

	uchroot chmod 660 /dev/fuse

	uchroot chown root.fuse /dev/fuse

I'm attaching my most up to date subsystem build for Ubuntu Precise.

[Christophe Bourcier]

You shouldn't mount bind /dev/fuse, because you will have issue if the group id of fuse is not the same in the host and in the subsystem.

After searching how to create properly /dev/fuse, here is what to do in the chroot:

Check if /dev/fuse exists:

ls -l /dev/fuse

if not, create it:

mknod /dev/fuse c 10 229

Check its rights:

ls -l /dev/fuse

must return:

crw-rw---T 1 root fuse 10, 229

If not fix it:

chmod 1660 /dev/fuse
chown root.fuse /dev/fuse

I have updated my howto with this information.

Christophe

[Vantz Stockwell]

Christophe,

Is it possible to get you to create an update chroot in en_US.UTF8 instead of french?

[cbourkier .]

Hi Vantz,

I have updated the OVD subsystems at http//lides.fr :

- default locale is en_US.UTF8

- default timezone is UTC

- bash has been updated to its latest version

Please give feedback.

Christophe

--
You received this message because you are subscribed to a topic in the Google Groups "Ulteo OVD Community Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ulteo-ovd-community-support/E11li3zkv9o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ulteo-ovd-community...@googlegroups.com.
To post to this group, send email to ulteo-ovd-com...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vantz Stockwell]

Thanks man testing now!

On Tuesday, October 7, 2014 4:10:53 PM UTC-4, Christophe Bourcier wrote:

Hi Vantz,

I have updated the OVD subsystems at http//lides.fr :

- default locale is en_US.UTF8

- default timezone is UTC

- bash has been updated to its latest version

Please give feedback.

Christophe

2014-10-07 4:21 GMT+02:00 Vantz Stockwell <vantz.s...@gmail.com>:

Christophe,

Is it possible to get you to create an update chroot in en_US.UTF8 instead of french?

On Monday, August 25, 2014 3:05:36 PM UTC-4, Christophe Bourcier wrote:

I have used this setup to create a 64-bit Debian Squeeze subsystem called from a Debian Wheezy server. For all the information, see http://lides.fr/cms/how-to-create-your-own-ovd-subsystem

For samba, I had to create a link from smbd to samba, so that it can be started by /etc/init.d/ulteo-ovd-subsystem:

cd /etc/init.d
ln -s samba smbd

But I still have the login bug described here https://groups.google.com/forum/#!topic/ulteo-ovd-community-support/gmBqqkHOrRU
I have to disable the fs role to be able to login. I have this bug also on a fresh OVD installation with the original subsystem.

--
You received this message because you are subscribed to a topic in the Google Groups "Ulteo OVD Community Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ulteo-ovd-community-support/E11li3zkv9o/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ulteo-ovd-community-support+unsub...@googlegroups.com.

[Vantz Stockwell]

I'm downloading the Ubuntu Precise 64-Bit will respond back once it's online.

On Tuesday, October 7, 2014 4:10:53 PM UTC-4, Christophe Bourcier wrote:

Hi Vantz,

I have updated the OVD subsystems at http//lides.fr :

- default locale is en_US.UTF8

- default timezone is UTC

- bash has been updated to its latest version

Please give feedback.

Christophe

2014-10-07 4:21 GMT+02:00 Vantz Stockwell <vantz.s...@gmail.com>:

Christophe,

Is it possible to get you to create an update chroot in en_US.UTF8 instead of french?

On Monday, August 25, 2014 3:05:36 PM UTC-4, Christophe Bourcier wrote:

I have used this setup to create a 64-bit Debian Squeeze subsystem called from a Debian Wheezy server. For all the information, see http://lides.fr/cms/how-to-create-your-own-ovd-subsystem

For samba, I had to create a link from smbd to samba, so that it can be started by /etc/init.d/ulteo-ovd-subsystem:

cd /etc/init.d
ln -s samba smbd

But I still have the login bug described here https://groups.google.com/forum/#!topic/ulteo-ovd-community-support/gmBqqkHOrRU
I have to disable the fs role to be able to login. I have this bug also on a fresh OVD installation with the original subsystem.

--
You received this message because you are subscribed to a topic in the Google Groups "Ulteo OVD Community Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ulteo-ovd-community-support/E11li3zkv9o/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ulteo-ovd-community-support+unsub...@googlegroups.com.

[Vantz Stockwell]

Well the Ubuntu 64-Bit on your website doesn't work on my VPS... I get failed everytime I try to start it. However the Debian 64-Bit does indeed work. Will update once I have more info and use with it with the new settings.

[Vantz Stockwell]

Yeah Christophe the new 4.0.2 Debian System works like a charm no issues. However as stated earlier I can't get the Ubuntu 4.0.2 base.tar.gz to work properly.

On Tuesday, June 10, 2014 5:20:23 PM UTC-4, Stuart England wrote:

Hey guys, not sure what its correct name is but is it possible to update the chroot environment from Lucid to something newer. Google have dropped support for Lucid which is causing me issues.

Better yet, is there a way to have a normal ubuntu server ({14.04 etc) serve up applications to ulteo rather than this chroot environment

thanks

Stuart

[Vantz Stockwell]

Ok Christophe in the Debian 64-Bit base.tar.gz the only issue I am running into is freezing once logged in.. but I think my VPS may need a fresh install so I am going to do that and try again tomorrow. If I come across anything I will let you know.. as for why Ubuntu isn't working I have no clue.

[Mico]

Sorry I mean this base.tar.gz from : https://www.dropbox.com/s/iomxihvp9x1wsaf/base.tar.gz?dl=0

Also instructions on using it at: http://openulteo.com/ulteo/Ubuntu%20Precise.pdf

On Tuesday, October 7, 2014 10:56:48 PM UTC-5, Mico wrote:

You can try https://www.dropbox.com/s/oor8h7t7yydz21f/ovd-sources-4.0.2.tar.gz?dl=0 for Ubuntu x64.  Bash needs to be updated and some other customization highlighted on openulteo.com/download

[Vantz Stockwell]

Mico I will test this base.tar.gz out tonight and let you know how it works this evening when I get off work. Should be around 10pm EST and post back on here. Thank you for your help!

[Vantz Stockwell]

I think I've found my problem my VPS kernels won't allow it. Unless I run the older versions so there is something in the newer packages Mico and Christophe have built that my kernel doesn't like. Going to try and on non virtualized kernel in Hyper-V.

[Mico]

Yeah, I think chroot requires kernels that support the sticky bit inside of chroot.

[Vantz Stockwell]

Mico it works just fine on Hyper-V 2012 R2 w/ CentOS 6.5 as the host.

[Vantz Stockwell]

Christophe I'm going to retest your chroot environments this weekend on a seperate VM on my home lab. I am ordering a dedicated server next weekend probably to start doing automated build testing. I would like to get the 4.0.2 source code updated to the latest versions of everything.

[Emessiri Kessiena]

Hello,

I don't know if you've resolved the issue, I hope you have as it is an old post. But I had the same issue with my VM, turns out it was a kernel module issue. Once I used a reserve kernel I had on my system, it worked perfectly.

Kind regards,

[yannick sudrie]

Hi Vantz,

sorry to exhume your 3years old post but have you share your docker(s) file(s) on git ?

Thanks !

Le lundi 25 août 2014 11:36:42 UTC+2, Vantz Stockwell a écrit :

Christophe,

I followed your directions however instead of using a chroot environment I'm using Docker for quicker testing... with Precise Pangolin 12.04 and OVD 4.0.2 however when I try to start Samba I get a launch error have you used this setup before?

On Sunday, June 29, 2014 3:54:19 PM UTC-4, Christophe Bourcier wrote:

Hi Stuart,

You can create an OVD subsystem in any of the distributions for which OVD has been packaged. The last version of Ubuntu supported is Precise Pangolin. See http://archive.ulteo.com/ovd/4.0.1/ubuntu/pool

The idea is to create a chroot of your favourite supported distribution (using debootstrap), add the Ulteo repository to apt sources list, and add the specific packages needed for a subsystem:
apt-get install ulteo-ovd-desktop ulteo-ovd-slaveserver ulteo-ovd-slaveserver-role-aps ulteo-ovd-slaveserver-role-fs uxda-server ulteo-ovd-externalapps-client ulteo-ovd-integrated-launcher ulteo-xfce4-restricted-menu-plugin libovd-xclient-area apache2 samba

You can try to install these packages in the main environment of your server instead of a chroot one. But at your own risk.

Christophe