We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello guys,
We have an error when we run herokuish image on offline environment!
This is an example with an java app:
docker run --rm -v / root / app /: / tmp / app gliderlabs / herokuish: v0.5.27 / bin / herokuish buildpack test -----> Java app detected / tmp / buildpacks / 05_buildpack-java / bin / test-compile: line 18: export_env: command not found 2021/04/02 08:52:33 exit status 127
docker run --rm -v / root / app /: / tmp / app gliderlabs / herokuish: v0.5.27 / bin / herokuish buildpack test
-----> Java app detected
/ tmp / buildpacks / 05_buildpack-java / bin / test-compile: line 18: export_env: command not found
2021/04/02 08:52:33 exit status 127
We have systematicaly, 'export_env command not found'.
To reproduce this, remove access to internet (with a firewall for exemple, leave port 22 anyway haha).
If you have an idea for resolv this, we would be very happy.
Thanks!
The text was updated successfully, but these errors were encountered:
It is up to a specific buildpack to support offline functionality. In this case, it's the heroku buildpack that forces the following url.
Feel free to ask upstream to make that an env var so you can overwrite it and we'll pull the update in. The python does it like so.
Sorry, something went wrong.
No branches or pull requests
Hello guys,
We have an error when we run herokuish image on offline environment!
This is an example with an java app:
docker run --rm -v / root / app /: / tmp / app gliderlabs / herokuish: v0.5.27 / bin / herokuish buildpack test
-----> Java app detected
/ tmp / buildpacks / 05_buildpack-java / bin / test-compile: line 18: export_env: command not found
2021/04/02 08:52:33 exit status 127
We have systematicaly, 'export_env command not found'.
To reproduce this, remove access to internet (with a firewall for exemple, leave port 22 anyway haha).
If you have an idea for resolv this, we would be very happy.
Thanks!
The text was updated successfully, but these errors were encountered: