You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built the docker image from the repository and it successfully runs and I am able to open the libTAS application, however when attempting to start a game I receive the following output
[libTAS f:0] Thread 51 (main) ERROR: tmp_fd != -1 failed in ProcSelfMaps with error Operation not supported
Attempt 1: Couldn't connect to socket.
Game couldn't start properly.
recv() returns -1 with error Bad file descriptor
The connection to the game was lost. Exiting
Based on the brief discussion in the discord here which suggests that the issue is O_TMPFILE not being supported on the file system, I ran df -T /usr in the docker container and confirmed that libTAS is installed in an overlay type filesystem. I confirmed that O_TMPFILE is not supported on this file system (related man page)
This means that the docker image can't be run using the recommended driver as per the Docker documentation, and the alternatives are all either deprecated, have poor performance, or require a certain backing file system.
The text was updated successfully, but these errors were encountered:
I built the docker image from the repository and it successfully runs and I am able to open the libTAS application, however when attempting to start a game I receive the following output
Based on the brief discussion in the discord here which suggests that the issue is
O_TMPFILE
not being supported on the file system, I randf -T /usr
in the docker container and confirmed that libTAS is installed in anoverlay
type filesystem. I confirmed thatO_TMPFILE
is not supported on this file system (related man page)This means that the docker image can't be run using the recommended driver as per the Docker documentation, and the alternatives are all either deprecated, have poor performance, or require a certain backing file system.
The text was updated successfully, but these errors were encountered: