why gc local up is suddenly firing up on 60001?

I’ve never encountered this. Did you submit an issue?

It will search for the next available port if the port is already in use.

@dpetrick I thought that, too. Here’s what I think it happened. For testing, I removed my

$HOME/.graphcoolrc

. I must’ve done that whilst docker was still running, so when I next run

gc local up

it opened on port 60001. However, I must have not noticed at all. I then restarted the whole Linux box where my stuff runs, and then executed a

gc local up

again. This time I did notice, but there were no other docker instances running, so I couldn’t figure it out. Until I remembered about

$HOME/.graphcoolrc

. When I removed it and then fired up docker via

gc

, a new instance of that file was created, saving the 60001 port in the configuration 🙂