`error: libcurl.so: cannot open shared object file: No such file or directory` about steamcmd

[CM2Walki]

@almereyda I still have some catching up to do with my other repositories, but I'll try to get it done on the weekend.

[serpi90]

Steamcmd is probably using the old version 3 of libcurl, installing libcurl3-gnutls should fix it.

[CM2Walki]

Steam>login [username] [password]
Logging in user '[username]' to Steam Public...
Enter the current code from your Steam Guard Mobile Authenticator app
Two-factor code:[SteamGuardCode]
OK
Waiting for client config...OK
Waiting for user info...OK

Steam>

I just tried it with the new bookworm and I'm not receiving this error.

Can you go and check if this fixes the issue?

[almereyda]

Thanks, I should try it again.

Is https://github.com/CM2Walki/CS2/issues/3 still considered to be merged at some point?

[almereyda]

This was a permission issue. You can see above that the .state/Steam volume has the permissions 0:0, while the image runs commands as 1000:1000. Changing the ownership of the directory prior running the container resolved the situation.

$ docker-compose run --rm login     
Creating cs2chnio_login_run ... done
…
Steam Console Client (c) Valve Corporation - version 1705108307
-- type 'quit' to exit --
Loading Steam API...OK
Logging in user 'account' to Steam Public...
This computer has not been authenticated for your account using Steam Guard.
Please check your email for the message from Steam, and enter the Steam Guard
 code from that message.
You can also enter this code at any time using 'set_steam_guard_code'
 at the console.
Steam Guard code:
OK
Waiting for client config...OK
Waiting for user info...OK

This is due to the way how Docker handles permissions in our system. Users that are running Docker commands via an unprivileged user or run the container in rootless mode or Podman may not experience this effect.

I might also have to try this Steam Guard Mobile Authenticator app some time.

Leaving this open to discuss if the container should be built in a way that it checks for being able to write to the volume mount, before initiating the login.