-
Notifications
You must be signed in to change notification settings - Fork 15
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
Disk space occupation ERROR #26
Comments
Thanks for letting us know. We'll look at this right away. |
@EUConsulting Are you using the latest version of this repository? Can you also share the steps to reproduce this error, please? |
I am using the latest version published by you (downloaded 2 days ago) and the latest version of docker To reproduce the fact, simply follow the steps you indicated (those for docker) and leave the container for a few minutes, you will immediately see that docker_data.vhdx in the path C:\Users\myuser\AppData\Local\Docker\wsl\disk will start to grow out of control. the script that produces the error is this : to avoid the problem i used this I had already reported this problem about 3 months ago on the Quality Portal (RSS-1076) Embarcadero and you had corrected it (in RSS-1076 you can find your answer). also fix the interbase docker image script let me know if I can be of further assistance |
@EUConsulting please, use the run.sh script, otherwise you need to provide the -t option by yourself. |
@EUConsulting we are also working in the new Docker image for InterBase. |
Even in the new PAServer version, creating the container via docker causes a space occupation estimated at 100 MB every 2/3 minutes of use
We have already reported this error (RSS-1076) that has been re-proposed in the new version:slight_frown:
We recommend checking and correcting the run.sh script with
one similar to this one that solves the problem
docker run --cap-add=SYS_PTRACE --security-opt seccomp=unconfined --platform linux/amd64 -it -e PA_SERVER_PASSWORD=MyPasswd -p 64211:64211-name mycontainer_name radstudio/paserver:latest
The text was updated successfully, but these errors were encountered: