# Connectivity issue

**URL:** <https://discuss.ipfs.tech/t/connectivity-issue/9158>\
**Category:** Help\
**Created:** [September 28, 2020, 1:43pm UTC](https://discuss.ipfs.tech/t/connectivity-issue/9158 "2020-09-28T13:43:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![horphi0815](https://avatars.discourse-cdn.com/v4/letter/h/2acd7d/32.png) [@horphi0815](https://discuss.ipfs.tech/u/horphi0815)\
**Post date:** [September 28, 2020, 1:43pm UTC](https://discuss.ipfs.tech/t/connectivity-issue/9158/1 "2020-09-28T13:43:35Z")

</div>

Hi,

i’m new in the ipfs exploring community.  
I try to run a ipfs service as docker container on my unraid.  
The container is running, but ipfs daemon tells me…

root@9dd44cfbd083:/# ipfs daemon  
Initializing daemon…  
go-ipfs version: 0.5.1-8c67a90723  
Repo version: 9  
System version: amd64/linux  
Golang version: go1.13.10

Error: lock /config/ipfs/repo.lock: someone else has the lock

do know this error?  
How can i unlock the repo?

Many thanks,

BR

Phil

---

<div class="post-metadata">

**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\
**Post date:** [September 28, 2020, 3:06pm UTC](https://discuss.ipfs.tech/t/connectivity-issue/9158/2 "2020-09-28T15:06:29Z")

</div>

Either a node hard crashed previously and didn’t cleaned the lock (but I think in this case IPFS would be able to detect that and cleanup the lock)  
Or much probable (because hard crash are really rare on GO), you already have an other instance of IPFS running (could be a `ipfs repo gc` or an other daemon).

---

<div class="post-metadata">

**Author:** ![horphi0815](https://avatars.discourse-cdn.com/v4/letter/h/2acd7d/32.png) [@horphi0815](https://discuss.ipfs.tech/u/horphi0815)\
**Post date:** [September 29, 2020, 11:20am UTC](https://discuss.ipfs.tech/t/connectivity-issue/9158/3 "2020-09-29T11:20:36Z")

</div>

> [@Jorropo](#):
>
> you already have an other instance of IPFS running (could be a `ipfs repo gc` or an other daemon).

this docker is a clean setup without any other installations.

Mhhh… thats hard figure out the root… i will try to find it

BR

---

<div class="post-metadata">

**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\
**Post date:** [September 29, 2020, 1:06pm UTC](https://discuss.ipfs.tech/t/connectivity-issue/9158/4 "2020-09-29T13:06:30Z")

</div>

could also be a left over lock that didn’t got cleaned (that pretty rare but can happen)  
If you are totaly sure of no other node running you can `rm -f` it (I don’t remember the path, but it should be in `~/.ipfs/` probably)