-
Notifications
You must be signed in to change notification settings - Fork 314
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
[docker exporter] Support non-service packages #5600
Comments
Example use case: I have a repository that has several scripts that are run as cron jobs to pull data out of various API services and toss that data into a database, or an S3 bucket, or other such purposes. I can export the docker container with
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
Don't close this. The fact that issues like this haven't been addressed is one of the primary reasons my org is moving away from all use of Habitat. The use of the stale bot just adds insult to injury. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details. |
Docker containers aren't just used for running services; they're frequently used to package tools (eg. the Habitat studio) and more. The docker exporter should support these use cases as well. Support should be added for:
The text was updated successfully, but these errors were encountered: