-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no window borders, no controls after container stop - start #37
Comments
Hello @samlnx03, thank you for you feedback. Unfortunatelly, I'm not able to reproduce the issue. Can you please closer describe your environment and the use case? Are you on Windows or Linux? Are you on the cloud? How do you start your container? Can you provide the statement? How do you stop and start the container? Do you use Have you overriden the container user? Have you bound any external volumes? Does it help, if you rename the folder Remark: You can rename it inside the running container, but you have to use For the comparison, this is what I get if I create the container like this: docker run -d -P --name testing --hostname testing accetto/ubuntu-vnc-xfce-g3 and this is after stopping and starting the conatiner again: Regards, |
I've just published Release 23.03 with Please let me know if it has solved your issue. |
Hello @samlnx03, while working on other issues, I was able to get sometimes similar behaviour you've described. However, it happens only if I bind the complete directory Have you also bound the complete I've prepared two images that fix it on my environment. Could you test them please and let me know, if they've helped? Regards, |
Hello accetto Yes, i use a local directory used as directory /home/headless/ That way I can check each student work out of the container I'll test you image as soon as possible |
Oh, now it's all clear. According my testing, binding the complete The reason for the behaviour is, that the container needs to initialize the You can quickly recognize that the container has not initialized correctly if you don't see the You have generally two possibilities. I would recommend, that you create a separate parent directory for the workspaces of your students. You can bind that folder without problems. It can be a subfolder of the You can also initialize the container first in some controlled environment. It can be the container itself, without any bindings, or using a named Docker volume for the There is one more thing. During my testing I've found, that if bind the whole I've found, that it happens because the image accetto/ubuntu-vnc-xfce-g3 doesn't include the package So, if you decide to bind the whole |
I'm removing the |
Hello and thanks in advance
everithing is running fine until I stop the container then start it again, initially the windows have their controls and borders but after de stop-start they don't. I saw wfm4 and /usr/lib/x86_64-linux-gnu/xfce4/exo-2/exo-helper-2 not present
what can I do in this cases whitout remove the container?
The text was updated successfully, but these errors were encountered: