Run container via a scheduled task on Synology

[Roberto277z]

I would like to be able to start a container via a basic command line:
docker container start rutorrent-vpn

However, when the nas runs the script, the container does not start and I get an error message :
line 1: docker: command not found

The script is running in Root.
The 1st script is the command: /usr/local/bin/docker container start rutorrent-vpn

The return is :
line 1: /usr/local/bin/docker: No such file or directory

On the other hand, I did inject the /usr/local/bin/docker into the PATH.
Here is the return of the $PATH export:
-sh: export: `/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin’: not a valid identifier

Could you please help me?

 

[Roger]

I use a task to start my portainer docker image. I do not call a script but call the command directly. And I run the task with user root. This works for me.

 

[Roberto277z]

I use a task to start my portainer docker image. I do not call a script but call the command directly. And I run the task with user root. This works for me.

View attachment 4626

View attachment 4627

Hello,

It doesn't work for me

==> line 1: /usr/local/bin/docker: No such file or directory

 

[Roger]

Hi,

May be the container does not exist? In my example I ran a new container.

 

[one-eyed-king]

The error message inidcates that docker (as in the commandline client) can't be found.

Seems something is off with your docker installation: either the docker package is stopped os ir broken somehow?

I would suggest to remove and reinstall the docker package, then try again.

 

[Roberto277z]

It's strange because, all of dockers are running :

If i'm launch this command by a script :
sudo docker-compose -f docker-compose.yml up -d

My error is :
docker-compose not found.

It's very strange because by entering the commands directly in SSH without going through a script it works

 

[Roberto277z]

No solution ?

 

[jphermans]

It's strange because, all of dockers are running :
View attachment 4672

If i'm launch this command by a script :
sudo docker-compose -f docker-compose.yml up -d

My error is :
docker-compose not found.

It's very strange because by entering the commands directly in SSH without going through a script it works

Then you have to install docker-compose or to update it when it's broken.

How to Update Docker Compose on a Synology NAS - WunderTech

This tutorial will show how you can update Docker Compose on a Synology NAS! Full instructions that will guide you through the whole process!

www.wundertech.net

 

[one-eyed-king]

No solution ?

Have you actualy ever tried to remove the docker package and reinstall it?

Your installation obviously is messed up or you have a race-condition. Just because some parts of docker work as expected, does not necessarily mean the whole docker package works as expected. In your case it does not.

Please add a ls -la before your docker line (I would have copied the string, if you wouldn't have shared it as screenshot). It will indicate whether the symlink to the docker binaries actualy exist at the point in time before your script starts, or does not exist.

You could delay the execution and wait for the symlink beeing available before you actualy run your docker command:

while [ ! -e /usr/local/bin/docker ]; do
  echo "waiting for the docker symlink"
  sleep 1
done
{your docker command here}

And on a closer look: why do you event want to use a scheduled task to restart a container?! The UI specificly provides a checkbox for this in the container settings.

 

[Roberto277z]

Have you actualy ever tried to remove the docker package and reinstall it?

Your installation obviously is messed up or you have a race-condition. Just because some parts of docker work as expected, does not necessarily mean the whole docker package works as expected. In your case it does not.

Please add a ls -la before your docker line (I would have copied the string, if you wouldn't have shared it as screenshot). It will indicate whether the symlink to the docker binaries actualy exist at the point in time before your script starts, or does not exist.

You could delay the execution and wait for the symlink beeing available before you actualy run your docker command:

while [ ! -e /usr/local/bin/docker ]; do
  echo "waiting for the docker symlink"
  sleep 1
done
{your docker command here}

And on a closer look: why do you event want to use a scheduled task to restart a container?! The UI specificly provides a checkbox for this in the container settings.

You are the best ! It works.

 

[schnill]

Then you have to install docker-compose or to update it when it's broken.

How to Update Docker Compose on a Synology NAS - WunderTech

This tutorial will show how you can update Docker Compose on a Synology NAS! Full instructions that will guide you through the whole process!

www.wundertech.net

Same here

It's strange because, all of dockers are running :
View attachment 4672

If i'm launch this command by a script :
sudo docker-compose -f docker-compose.yml up -d

My error is :
docker-compose not found.

It's very strange because by entering the commands directly in SSH without going through a script it works

This worked for me:

Task script:

#!/bin/bash
cd /volume1/docker/[directory where docker-compose.yml is stored]/
sh ../update.sh

update.sh in the directory /volume1/docker:

docker-compose down && docker-compose pull && docker-compose up -d

You could include a docker-compose rm -f in order to make sure the container is cleaned up:

docker-compose down && docker-compose rm -f && docker-compose pull && docker-compose up -d

Also, you could replace the && with ; or & in order to make sure the container runs should the cleaning or pull fail for whatever reason.