Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supercronic does not inherit env variables #352

Closed
necmettin opened this issue Jan 8, 2023 · 4 comments
Closed

Supercronic does not inherit env variables #352

necmettin opened this issue Jan 8, 2023 · 4 comments
Labels
bug Something isn't working stale Issues inactives for a while (automatically)

Comments

@necmettin
Copy link

Expected Behavior

Supercronic should inheric ENV variables

Current Behavior

Supercronic does not inherit ENV variables

Possible Solution

Steps to Reproduce (for bugs)

  1. Set an ENV variable var: testing in your Dockerfile.
  2. Create cronjob to echo $var
  3. Output does not include the testing word.
    Sample output:
time="2023-01-08T16:24:59+03:00" level=info msg=starting iteration=9 job.command="echo " job.position=0 job.schedule="* * * * *"
time="2023-01-08T16:25:00+03:00" level=info channel=stdout iteration=9 job.command="echo " job.position=0 job.schedule="* * * * *"
time="2023-01-08T16:25:00+03:00" level=info msg="job succeeded" iteration=9 job.command="echo " job.position=0 job.schedule="* * * * *"

Context

I'm trying to send certain variables to PHP and Supercronic. For example, a database URL. ENV is sent to PHP processes, but not to supercronic.

Your Environment

docker-compose.yml.txt

  • Version used: thecodingmachine/php:8.2-v4-fpm
  • Operating System and version: MacOS 12.6.2. Monterey
@stale
Copy link

stale bot commented Mar 9, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please update it if any action still required.

@stale stale bot added the stale Issues inactives for a while (automatically) label Mar 9, 2023
@necmettin
Copy link
Author

Guess I need to ping this?

@stale stale bot removed the stale Issues inactives for a while (automatically) label Mar 10, 2023
@mistraloz mistraloz added the bug Something isn't working label Mar 13, 2023
@stale
Copy link

stale bot commented May 12, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please update it if any action still required.

@stale stale bot added the stale Issues inactives for a while (automatically) label May 12, 2023
@stale
Copy link

stale bot commented May 19, 2023

This issue has been automatically closed because it has not had recent activity. Please, reopen if you need.

@stale stale bot closed this as completed May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issues inactives for a while (automatically)
Projects
None yet
Development

No branches or pull requests

2 participants