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
Thank you for the work on this project, it looks like a great solution to running Cron in a secure containerised environment.
I'd like to suggest that this project provide images on Docker Hub. The main advantage I see to doing this would be that for using Supercronic in a project, I could simply use the COPY directive in my Dockerfile to copy the binary from the most appropriate Supercronic image.
For example, the PHP Composer project does this and in a Dockerfile I simply need to include the following: COPY --from=composer:2 /usr/bin/composer /usr/bin/composer
This line ensures that I always have the most up to date build of Composer 2 in my final image, and (while not applicable to Composer) Docker would know which architecture I need, making my Dockerfile more portable across different architectures (x86, ARM, etc).
Thanks,
-Aaron
The text was updated successfully, but these errors were encountered:
AaronMcHale
changed the title
Suggestion: make available on Docker Hub
Suggestion: Make images available on Docker Hub
Feb 26, 2021
Thank you for the work on this project, it looks like a great solution to running Cron in a secure containerised environment.
I'd like to suggest that this project provide images on Docker Hub. The main advantage I see to doing this would be that for using Supercronic in a project, I could simply use the
COPY
directive in my Dockerfile to copy the binary from the most appropriate Supercronic image.For example, the PHP Composer project does this and in a Dockerfile I simply need to include the following:
COPY --from=composer:2 /usr/bin/composer /usr/bin/composer
This line ensures that I always have the most up to date build of Composer 2 in my final image, and (while not applicable to Composer) Docker would know which architecture I need, making my Dockerfile more portable across different architectures (x86, ARM, etc).
Thanks,
-Aaron
The text was updated successfully, but these errors were encountered: