Before this, I have used a Window container for docker and never face issues with code 139.
Then I changed to WSL (Windows Subsystem for Linux) container for the purpose to improve the performance.
But by using WSL I can't start a certain image, the container keeps restarting. This restarting state makes it is impossible to see the container logs by using the command $ docker logs -f <container>.
Hence instead of using $ docker-compose up -d I use $ docker-compose up so I can see the logs during the start.
sample
So somewhere I read this 139 related to system unable to access so location due to permission issues. Then to solve this issue at WSL by updating the .wslconfig by adding
kernelCommandLine = vsyscall=emulate
Step 1 : Create a file named .wslconfig in your user directory
Ex:- C://users/[your user name]/.wslconfig
Step 2 : Add following line to the .wslconfig file
kernelCommandLine = vsyscall=emulate
0 comments:
Post a Comment