Add disk write error troubleshooting info to troubleshooting.md
Add cont-init.d script to check for the library configuration and steamapps folder, and create it if it doesn't exist.
Using the latest image, I was able to reproduce the error observed in issue #57.
/mnt/games/GameLibrary/SteamLibrary/libraryfolder.vdf gets created, but steamapps does not.
Steam has to execute and configure itself for the first time to create the vdf file in the folder mount, but for some reason it will not create the steamapps folder. I do not know of a way to have the desktop entrypoint execute steam, and then wait for it to be installed/configured in parallel for waiting for steam to finish running.
The best solution I could come up with was adding this to init.d, but would require a second boot of the container after the initial execution of the container.
Let me know if you have any other ideas or avenues I can explore, otherwise, upon first install, the solution would be to:
1) execute the container
2) let steam install and update
3) restart the container
docker-compose.mdtroubleshooting.mdUsing the latest image, I was able to reproduce the error observed in issue #57.
/mnt/games/GameLibrary/SteamLibrary/libraryfolder.vdfgets created, butsteamappsdoes not.Steam has to execute and configure itself for the first time to create the vdf file in the folder mount, but for some reason it will not create the steamapps folder. I do not know of a way to have the desktop entrypoint execute steam, and then wait for it to be installed/configured in parallel for waiting for steam to finish running.
The best solution I could come up with was adding this to init.d, but would require a second boot of the container after the initial execution of the container.
Let me know if you have any other ideas or avenues I can explore, otherwise, upon first install, the solution would be to:
1) execute the container 2) let steam install and update 3) restart the container