New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chown command doesn't exist on docker toolbox #18
Comments
Can you please try following?
I tested on ubuntu and it is equivalent. You will need to |
Ok, I did as you said. Note: the Now, it seem the script is stuck there:
Maybe the docker commands doesn't deal with regular "/" on the Windows platform? (similar issue are using //) edit: Well, look like this is the same issue as #15, so this can be closed. |
Can you run just the docker run command?
|
I edited the / vs \ |
Your command didn't work(
Now I guess |
It could be because I made some further changes to game finished detection :) Maybe retry with master? So all I have to do for docker toolbox on windows is to replace Doesn't that break docker for windows? |
I could test both commands tomorrow morning, when I will be in the office (GMT+6). I run |
On |
Does it matter if it is forward/backward slash? |
|
So this should be enough?
and then
|
This should works for me, but we should wait @antogerva until it test without |
The code snippet I've posted does only the |
@michalsustr Sound good, I guess the one-letter replacement is how it should be in case of weird symlink to an another drive, etc. I attempted to build these docker images locally on docker-toolbox and see if I could test, but I got stuck there:
So, I guess I should wait for an update on Docker Hub for further tests. |
I saw there's an update on DockerHub. Now I get the following output. Also, I realized I could just modify
Now, I get the following output:
Look like the container failed to launch. I'm not sure if I'm missing something... edit: I mean, can I get additionnal log on what might have failed? |
@antogerva The container could failed to launch (but more specifically immediately close after launch) if there already exist replay files. Since you probably try launch games multiple times, GAME_33884C27_0_krasi0 and GAME_33884C27_1_CherryPi replays probably already here. |
Ok, I did more tests and turn out on docker-toolbox, the drive-letter need to be lower case. I also removed completly the backslash. I fixed this with the following code:
Now, I believe there's one last issue. Look like loopback connection is disabled on the VNC server?
So, I look up what's going on and added
The image update went well. Yet, it seem adding |
Great, I'll use the drive letter function you posted. Why is there different IP? I thought it should be on the local net: |
@michalsustr Look like the only way to get localhost to work on docker-toolbox is to directly modify some settings in virtualbox about port fowarding. |
expected behaviour
The VNC viewer should start without issue on
Docker Toolbox
. The commandscbw.play
shouldn't required to work only withDocker for Windows
(which require Hyper-V). The pactual behaviour
scbw.play crash when performing while it
chown
doesn't exist on docker toolbox for window.There should be a workaround instead of using:
COPY --chown=starcraft:users starcraft.zip $SC_DIR
I did a bit of search about the issue and found this. So maybe using usermod could fix this issue.
RUN usermod -u 1000 $SC_DIR
steps to reproduce
operating system
windows 10
note: i tried on ubuntu without issue
docker version
output of command
docker version
:$ docker version
Client:
Version: 17.07.0-ce
API version: 1.26 (downgraded from 1.31)
Go version: go1.8.3
Git commit: 8784753
Built: Tue Aug 29 17:41:05 2017
OS/Arch: windows/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: linux/amd64
Experimental: false
scbw version
output of command
scbw.play -v
0.2a19
The text was updated successfully, but these errors were encountered: