deleteing dockerimages messes things up

[peter1000]

I installed subuser firefox and had some issues not running the subuser version.
I stopped the docker: sudo service docker stop

cause I had old docker stuff hanging around I deleted the whole docker folder: /var/lib/docker because of issue moby/moby#2714 (comment)

restart docker: sudo service docker start

subuser is completely messed up (understandable as it has still the installed-programs.json ect)

maybe in the future subuser could self heal a brocken situation like this

[timthelion]

Unfortunately, I'm not sure if I understand you fully:

1. You installed firefox with subuser.
2. You then wanted to start up the "normal" firefox.
3. You couldn't, so you tried to delete everything bellonging to docker.
4. That still didn't help and now both versions of firefox were borked.

---

OR do you mean:

---

1. You had some problem with something else related to docker.
2. You decided to clean house and delete everything bellonging to docker.
3. Afterwards, the subuser version of firefox was borked.

---

I've attempted to fix both problems. If an image dissapears, then the user is prompted to reinstall the program the next time they try to run that program.

Is this good?

I'd also like to add this feature eventually: #23 it really won't be difficult.

[peter1000]

I had old docker stuff around from yesterday.

I installed subuser to test it out

I installled subuser firefox and thought it was not working

Only later I found out that:
the real issue was I had already an ubuntu host firefox open 
and in such an case subuser firefox seems not to work

maybe something to check or to mention somewhere

anyhow in the beginning I thought subuser firefox does not work: maybe it was because of the old docker stuff

so I deleted all docker things and restarted the docker service

subuser was messed up

[timthelion]

OK, I have no idea why running firefox as host would interfere with running firefox under docker. Is this on Unity? Perhaps this is a Unity bug/confusion, they have something weird going on where they group applications by name, and refuse to start a new instance of an application that's already running. I'm not on ubuntu, but as soon as I get a chance I'll check this out.

Tim

[peter1000]

not sure either: just installed ubuntu 13.10 recently because of docker: but I do not use the unity login instead the Classic Gnome.