3

I recently created a docker-compose file here: https://github.com/ffMathy/Screeps.Server.Docker/blob/master/docker-compose.yml

I'm currently on Windows, but running Linux containers.

When I try to start up my containers using docker-compose up, they appear just fine. However, the screeps container doesn't show anything in the log, and doesn't start (I know this because I can't connect to its port).

Now, if I then click the volume via Kitematic (as shown in the screenshot) and click "Enable volumes" in the prompt that shows, the container restarts, and works - logs are also present in the preview as expected.

enter image description here enter image description here

I don't understand how this can affect the container itself - that doesn't make much sense to me.

Mathias Lykkegaard Lorenzen
  • 15,031
  • 23
  • 100
  • 187

2 Answers2

4

I'm having the same exact issue.

Downgrade Kitematic to 0.17.6 seems to fix the problem.

You can download it from here:

https://github.com/docker/kitematic/releases/tag/v0.17.6

Daniel Krom
  • 9,751
  • 3
  • 43
  • 44
  • This resolved the logging issue, but not the issue causing container to not start unless I click "Enable volumes". – Mathias Lykkegaard Lorenzen Apr 21 '19 at 13:40
  • @MathiasLykkegaardLorenzen Is this for a specific container or for everyone? – Daniel Krom Apr 23 '19 at 10:34
  • There might be an error/typo in the docker-compose file: The volume screeps-volume is defined but not actually used. What is used is a local directory: "./screeps-volume". Could you fix the file to use the actual volume by removing the "./" part and try again? – Mihai Apr 23 '19 at 11:02
2

I solved the problem by forcing the volume to mount to a relative path in my docker-compose.yml file.

Mathias Lykkegaard Lorenzen
  • 15,031
  • 23
  • 100
  • 187