# Node stopped working as docker container on qnap-container-station

**URL:** <https://forum.storj.io/t/node-stopped-working-as-docker-container-on-qnap-container-station/27973>\
**Category:** troubleshooting\
**Tags:** docker, qnap-nas\
**Created:** [September 20, 2024, 4:13pm UTC](https://forum.storj.io/t/node-stopped-working-as-docker-container-on-qnap-container-station/27973 "2024-09-20T16:13:02Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [September 22, 2024, 3:17am UTC](https://forum.storj.io/t/node-stopped-working-as-docker-container-on-qnap-container-station/27973/13 "2024-09-22T03:17:23Z")

</div>

@Scriptiee actually can be right. Do you have an `exec` mount option for the disk with data?  
You may check your `/etc/mtab`.  
The image

> [@beli](#):
>
> storjlabs/storagenode:2159415

has a change, where binaries are now located in the `bin` subfolder of the data location.  
You need to check the docker container logs, not redirected logs, because a supervisor is printing messages only to the docker container logs.

```auto
docker logs storagenode

```

See also:

> [@Spawnerr: no permission to run command](https://forum.storj.io/t/spawnerr-no-permission-to-run-command/27962/15):
>
> I was able to resolve my issue after some trial and error. My fstab config needed updating AND my bin folder needed to be executable. I tried defaults 0 2, but without nofail my system failed to boot and it took some time to mount the drive to another system to update the fstab. Final fstab settings: defaults,noatime,nofail 0 2 Full fstab file and output of ls -l /mnt/storj/storj\_data:

---

_[View the full topic](https://forum.storj.io/t/node-stopped-working-as-docker-container-on-qnap-container-station/27973)._