Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
I remember having the same issue, but can't remember what I did to fix it
Also, most importantly: Docker is useful for stateless containers. Using your container to update something inside it is probably not the most ideal usage of it.
Containerization is useful for isolation of things. Some would argue that's the main point. Especially when trying out some new tech it's nice to have the environment preconfigured even if you're gonna pull some data in there. Anyway, that's off topic.
ZIP-Folder and started SteamCMD while looking in the ZIP-Folder and starting the .exe from there.
So please check that you unzipped SteamCMD ZIP-Folder before using SteamCMD.