You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start a container with the v1.xx version of docker-compose:
docker-compose up -d <service>
the resulting container name will be: <project_name>_<service>_1
Job runs great.
When i use the go version or a v2.xx version:
docker compose up -d <service>
the resulting container name will be: <project_name>-<service>-1
See dash vs. underscore in container name.
I think docker-crontab might have the underscore (_) burnt in somewhere and tries to find the container to run the script in using that separator (/opt/crontab/projects/*.sh):
Great work thanks!
When I start a container with the v1.xx version of docker-compose:
docker-compose up -d <service>
the resulting container name will be:
<project_name>_<service>_1
Job runs great.
When i use the go version or a v2.xx version:
docker compose up -d <service>
the resulting container name will be:
<project_name>-<service>-1
See dash vs. underscore in container name.
I think docker-crontab might have the underscore (_) burnt in somewhere and tries to find the container to run the script in using that separator (/opt/crontab/projects/*.sh):
And the job won't run as would not find a running container.
The text was updated successfully, but these errors were encountered: