BITNAMI - Custom (and not custom) workspaces lost after some time and reboot and ip changed

Custom (and not custom) workspaces lost after some time and reboot and ip changed

Reproduction Steps:

1. Running Bitnami image in virtualbox on windows 10 anniversary update 64bit

2. Installed php from “ready to go” tab

3. Installed Bitnami Express recipe under “stack library tab”

4. Some errors in creating new workspaces (typos…)

5. I’ve created custom stacks (ubuntu node 4.x with harp ) filling the textarea into the “custom stack” tab. Everything was working correctly. Here is the recipe I’ve provided

   FROM codenvy/ubuntu_jre
   
   RUN sudo apt-get update
   RUN sudo apt-get -y install build-essential libssl-dev libkrb5-dev gcc make ruby-full rubygems-integration python
   RUN curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
   RUN sudo apt-get install -y nodejs
   
   EXPOSE 9000 9001 9002 5000 3000
   
   RUN sudo npm install -g harp 
   
   WORKDIR /projects
   
   CMD tail -f /dev/null
   

6. created various projects and installed others dependencies

7. stopped workspaces and created snapshots

8. shutted down the virtual machine sudo shutdown - h now

9. shutted down the computer

10. I went to sleep 😉

11. Wake up the day after

12. Restarted the computer and the virtual machine (everything fine)

13. obtained new ip (dhcp)

Expected behavior:

Find all the previous workspaces created after loggin in in the new ip (chenged over night due to dhcp)

Observed behavior:

Find only php workspace. In the folder /opt/bitnami/apps/eclipseche/che/workspaces every project is still there.

Che version: 4.7.2-0 (64-bit)
OS and version: windows 10 anniversary / ubuntu 14.04 Docker version: 1.12.1 Che install: Bitnami on Virtualbox 5.1.6 r110634 (Qt5.5.1)

Additional information:

• Problem started happening recently, didn’t happen in an older version of Che: No
• Problem can be reliably reproduced, doesn’t happen randomly: No

Thank you

[bmicklea]

@amrecio - we thought that the Bitnami images had been updated to use Che 5.0, but the link posted above still shows 4.7.1. Can you help here?

[ghost]

Closing the issue. @matteo-bombelli feel free to reopen if the problem persists.