Portainer on Synology DSM 6.2

[niXta1]

Hi!
I'm running the :latest (1.17.1) Portainer on my Synology DSM 6.2 with docker 17.05.0-0370 (17.05.0-ce).

When I go to stats on any of my containers I get:

Failure
Unexpected pid '+': strconv.Atoi: parsing "+": invalid syntax

Command used to start Portainer:

sudo docker run -d \
--name Portainer \
--restart=unless-stopped \
-p 9000:9000 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portainer_data:/volume1/docker/portainer_data/portainer \
portainer/portainer:latest

[aiminickwong]

"-v portainer_data:/volume1/docker/portainer_data/portainer "
should be
"-v /volume1/docker/portainer_data/portainer:/data"

[deviantony]

@niXta1 do you have access to the Docker CLI ? If so, can you try to do a docker stats <CONTAINER_NAME> on the CLI? And docker top <CONTAINER_NAME> as well?

[niXta1]

Wow, missed that one. Fixed the data folder but it's empty and problem persist.

sudo docker stats <CONTAINER_ID>

Shows:

CONTAINER                                                          CPU %               MEM USAGE / LIMIT    MEM %               NET I/O             BLOCK I/O           PIDS
a27b9ec69255b2189193532a9e2f3e714dcbee92116f213c7c4f1cf025e2640f   1.87%               3.79GiB / 7.787GiB   48.67%              1.62TB / 259GB      0B / 0B             0

Looks ok to me.

sudo docker top <CONTAINER_ID>
Error response from daemon: Unexpected pid '+': strconv.Atoi: parsing "+": invalid syntax

I guess this is my problem and I need to talk to synology about this?

[deviantony]

Yes @niXta1 it seems that there is something wrong with your Docker engine/setup. Portainer proxies requests to the Docker API so this is why you're also seeing the same error message.

[lwitt]

Hi,
I have exactly the same issue after upgrading to DSM 6.2 (more or less mandatory if you want to run a Synology device securely).
Is there any progress or a possible workaround?

[niXta1]

I reported the "docker top" error to Synology but never got an answer...

[lwitt]

The strange fact is that Synology only provides a proprietary GUI on top of "standard" docker install.. I tried to use command line with exactly the same result.

[niXta1]

I got escalated to devs at Synology, top fails because I had an account name with an illegal character in it (space).
After removing the space it works as expected.
@lwitt, do try this workaround.

[petarDenevFlutterint]

Many years later but with the same problem. And I found the solution.
The problem: the linux distro do not have 'ps' command installed. (Example Amazon Linux do not have it)
The solution: Install procps using apt-get or yum. Here is a link with examples: https://ioflood.com/blog/install-ps-command-linux