Paketo Buildpacks
Replies: 3 comments 11 replies
-
|
So the fact that it's not printing the configuration is quite odd and definitely a bug. We like to print the configuration when the buildpack runs so it's clear what settings are being used. That should be happening but it's not. I'll take a look and see if I can sort out why. There's a strong possibility that this is just a display bug though. It does seem to be reading your settings because it's saying What specifically are you concerned with? Is it just the lack of output or are you seeing some other issue? PS. I would strongly recommend using |
Beta Was this translation helpful? Give feedback.
-
|
Fix for the bug in https://github.com/paketo-buildpacks/ca-certificates/releases/tag/v3.8.2 |
Beta Was this translation helpful? Give feedback.
-
|
I'm using both |
Beta Was this translation helpful? Give feedback.
-
|
Log changed : But I still see |
Beta Was this translation helpful? Give feedback.
-
|
That is expected. It's because you're setting When |
Beta Was this translation helpful? Give feedback.
-
|
I'm running the container in read only so I don't need a runtime layer, but it looks still active . One minut later : I have few times per day some issues with TLS, some servers are not reconized valid. So my intuition is that the truststore is not valid few milliseconds per minut, and if my program needs to use the truststore at that specific moment, it do not work. |
Beta Was this translation helpful? Give feedback.
-
|
Allright, thank you @dmikusa. I have exactly the same issue reported on the link you've provided paketo-buildpacks/libjvm#398 |
Beta Was this translation helpful? Give feedback.
-
|
Can you confirm we cannot use the paketo-buildpacks/environment-variables to set THC_PORT and THC_PATH venvs ? I would expect this configuration to be good enought, but it's not: <env>
<BPE_DELIM_JAVA_TOOL_OPTIONS xml:space="preserve"> </BPE_DELIM_JAVA_TOOL_OPTIONS>
<BPE_APPEND_JAVA_TOOL_OPTIONS>${WORKER_JVM_OPTION} -Djava.net.preferIPv4Stack=true
</BPE_APPEND_JAVA_TOOL_OPTIONS>
<!-- Add a healthcheck cli -->
<BP_HEALTH_CHECKER_ENABLED>true</BP_HEALTH_CHECKER_ENABLED>
<!-- Configure ca-certificates layer -->
<BP_RUNTIME_CERT_BINDING_DISABLED>true</BP_RUNTIME_CERT_BINDING_DISABLED>
<BP_EMBED_CERTS>true</BP_EMBED_CERTS>
<!-- Configure healthcheck cli to perform the healthcheck on specific port and path -->
<BPE_OVERRIDE_THC_PORT>9093</BPE_OVERRIDE_THC_PORT>
<BPE_OVERRIDE_THC_PATH>/actuator/health</BPE_OVERRIDE_THC_PATH>
<THC_PORT>9093</THC_PORT>
<THC_PATH>/actuator/health</THC_PATH>
</env>Current workaround requires to force THC_PORT and THC_PATH to be set on the container, ignoring any configuration on the source code, whether using BPE_*, or direct configuration on the healthcheck layer. |
Beta Was this translation helpful? Give feedback.
-
You cannot. The workaround is to call the tiny health checker directly, and by pass the launcher. However, the launch is what sets up the environment variables so when you bypass the launcher, you bypass the ability to set env variables on the app image itself. The health-checker buildpack normally sets these automatically, but when you switch to the workaround, that will stop working. Using the environment-variables buildpack is no different, they all depend on the launcher to set those before the process starts. If you need to set those, then you have to do it with your runtime configuration. If you're using Docker to run the app, you can use a |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your very relevant support; we were able to at least identify why we were having this error. I find it unfortunate to have boilerplate on the deployment side, but thanks to you, I can quickly deploy a fix for this issue. To be honest, your technology stack is completely watertight for a simple developer like me (not used to Go and Docker layers...), so I can only thank you for taking the time to fix the issues I raised. |
Beta Was this translation helpful? Give feedback.
-
I do as well. There are some technology limitations. What I'd really like is to have this information included in the image metadata, like you can do with a Dockerfile. That has to be changed at the buildpacks level. I put an RFC in to make that change, but it'll probably take some time, buildpacks/rfcs#309. If you want to follow that. Thanks for your patience with this and glad to hear you're enjoying the software! |
Beta Was this translation helpful? Give feedback.
-
|
For what it's worth, we've released health-checker 2.0.0, which removes the Please note that since we're not using the launcher to invoke the health check binary, we cannot set env variables on the image at build time. All environment variables to configure the health check binary must be set when you run the container. The release notes are here: https://github.com/paketo-buildpacks/health-checker/releases/tag/v2.0.0 |
Beta Was this translation helpful? Give feedback.
-
I've created a SO post but I do not have any response yet. So I'm trying here, hope it's the right channel
On the paketo-buildpacks/ca-certificates project, they provide 2 configurations using environment variable :
BP_RUNTIME_CERT_BINDING_DISABLEDandBP_ENABLE_RUNTIME_CERT_BINDING.But I don't find any documentation to provide such properties from the maven configuration :
As you can see on the log, it does not work. There is no
Build Configuration:on the ca-certificates module whereas the healthcheck module checks for its configuration parameter.Any idea where the issue is ? I don't know how to start with all theses project linked together
Beta Was this translation helpful? Give feedback.
All reactions