Closed pbrumm closed 2 weeks ago
I have a simple rails app and after upgrading to datadog 4x and nodejs@2.1.0 it pulls in too many buildpacks and fails
I rolled back the nodejs@2.0.0 and datadog@3.6.0 and that resolves the issue.
it suddenly pulled in
Step #2: Creating builder with the following buildpacks: Step #2: -> 'paketo-buildpacks/dotnet-core@0.42.3' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.6' Step #2: -> 'paketo-buildpacks/dotnet-core-aspnet-runtime@0.4.2' Step #2: -> 'paketo-buildpacks/dotnet-core-sdk@0.14.3' Step #2: -> 'paketo-buildpacks/dotnet-execute@0.14.26' Step #2: -> 'paketo-buildpacks/dotnet-publish@0.12.25' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/icu@0.7.3' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/node-engine@3.0.1' Step #2: -> 'paketo-buildpacks/procfile@5.6.7' Step #2: -> 'paketo-buildpacks/vsdbg@0.3.7' Step #2: -> 'paketo-buildpacks/watchexec@2.8.6' Step #2: -> 'paketo-buildpacks/go@4.6.2' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.6' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/git@1.0.7' Step #2: -> 'paketo-buildpacks/go-build@2.1.2' Step #2: -> 'paketo-buildpacks/go-dist@2.4.4' Step #2: -> 'paketo-buildpacks/go-mod-vendor@1.0.27' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/procfile@5.6.7' Step #2: -> 'paketo-buildpacks/watchexec@2.8.6' Step #2: -> 'paketo-buildpacks/java-native-image@8.25.0' Step #2: -> 'paketo-buildpacks/bellsoft-liberica@10.4.4' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.7' Step #2: -> 'paketo-buildpacks/datadog@4.8.0' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/executable-jar@6.8.3' Step #2: -> 'paketo-buildpacks/gradle@7.7.1' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/leiningen@4.6.9' Step #2: -> 'paketo-buildpacks/maven@6.15.12' Step #2: -> 'paketo-buildpacks/native-image@5.12.7' Step #2: -> 'paketo-buildpacks/procfile@5.6.8' Step #2: -> 'paketo-buildpacks/sbt@6.12.11' Step #2: -> 'paketo-buildpacks/spring-boot@5.27.8' Step #2: -> 'paketo-buildpacks/syft@1.42.0' Step #2: -> 'paketo-buildpacks/upx@3.4.7' Step #2: -> 'paketo-buildpacks/java@10.6.0' Step #2: -> 'paketo-buildpacks/apache-tomcat@7.14.2' Step #2: -> 'paketo-buildpacks/apache-tomee@1.8.0' Step #2: -> 'paketo-buildpacks/azure-application-insights@5.17.3' Step #2: -> 'paketo-buildpacks/bellsoft-liberica@10.4.4' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.7' Step #2: -> 'paketo-buildpacks/clojure-tools@2.8.14' Step #2: -> 'paketo-buildpacks/datadog@4.8.0' Step #2: -> 'paketo-buildpacks/dist-zip@5.6.8' Step #2: -> 'paketo-buildpacks/encrypt-at-rest@4.5.13' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/executable-jar@6.8.3' Step #2: -> 'paketo-buildpacks/google-stackdriver@8.0.4' Step #2: -> 'paketo-buildpacks/gradle@7.7.1' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/jattach@1.4.9' Step #2: -> 'paketo-buildpacks/java-memory-assistant@1.4.9' Step #2: -> 'paketo-buildpacks/leiningen@4.6.9' Step #2: -> 'paketo-buildpacks/liberty@3.8.12' Step #2: -> 'paketo-buildpacks/maven@6.15.12' Step #2: -> 'paketo-buildpacks/node-engine@3.1.0' Step #2: -> 'paketo-buildpacks/procfile@5.6.8' Step #2: -> 'paketo-buildpacks/sbt@6.12.11' Step #2: -> 'paketo-buildpacks/spring-boot@5.27.8' Step #2: -> 'paketo-buildpacks/syft@1.42.0' Step #2: -> 'paketo-buildpacks/watchexec@2.8.7' Step #2: -> 'paketo-buildpacks/yarn@1.2.0' Step #2: -> 'paketo-buildpacks/nodejs@2.0.0' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.6' Step #2: -> 'paketo-buildpacks/datadog@3.6.0' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/node-engine@3.0.1' Step #2: -> 'paketo-buildpacks/node-run-script@1.0.14' Step #2: -> 'paketo-buildpacks/node-start@1.1.3' Step #2: -> 'paketo-buildpacks/npm-install@1.3.1' Step #2: -> 'paketo-buildpacks/npm-start@1.0.15' Step #2: -> 'paketo-buildpacks/procfile@5.6.7' Step #2: -> 'paketo-buildpacks/watchexec@2.8.6' Step #2: -> 'paketo-buildpacks/yarn@1.2.0' Step #2: -> 'paketo-buildpacks/yarn-install@1.2.2' Step #2: -> 'paketo-buildpacks/yarn-start@1.1.3' Step #2: -> 'paketo-buildpacks/php@2.12.0' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.7' Step #2: -> 'paketo-buildpacks/composer@0.6.6' Step #2: -> 'paketo-buildpacks/composer-install@0.3.21' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/httpd@0.7.15' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/nginx@0.15.7' Step #2: -> 'paketo-buildpacks/php-builtin-server@0.4.22' Step #2: -> 'paketo-buildpacks/php-dist@2.2.0' Step #2: -> 'paketo-buildpacks/php-fpm@0.2.23' Step #2: -> 'paketo-buildpacks/php-httpd@0.3.23' Step #2: -> 'paketo-buildpacks/php-memcached-session-handler@0.2.22' Step #2: -> 'paketo-buildpacks/php-nginx@0.3.8' Step #2: -> 'paketo-buildpacks/php-redis-session-handler@0.2.23' Step #2: -> 'paketo-buildpacks/php-start@0.4.23' Step #2: -> 'paketo-buildpacks/procfile@5.6.8' Step #2: -> 'paketo-buildpacks/watchexec@2.8.7' Step #2: -> 'paketo-buildpacks/procfile@5.6.8' Step #2: -> 'paketo-buildpacks/python@2.14.0' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.3' Step #2: -> 'paketo-buildpacks/conda-env-update@0.7.12' Step #2: -> 'paketo-buildpacks/cpython@1.9.0' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.3' Step #2: -> 'paketo-buildpacks/image-labels@4.5.2' Step #2: -> 'paketo-buildpacks/miniconda@0.8.5' Step #2: -> 'paketo-buildpacks/pip@0.18.0' Step #2: -> 'paketo-buildpacks/pip-install@0.6.0' Step #2: -> 'paketo-buildpacks/pipenv@1.19.0' Step #2: -> 'paketo-buildpacks/pipenv-install@0.6.18' Step #2: -> 'paketo-buildpacks/poetry@0.6.5' Step #2: -> 'paketo-buildpacks/poetry-install@0.3.17' Step #2: -> 'paketo-buildpacks/poetry-run@0.4.21' Step #2: -> 'paketo-buildpacks/procfile@5.6.4' Step #2: -> 'paketo-buildpacks/python-start@0.14.14' Step #2: -> 'paketo-buildpacks/watchexec@2.8.3' Step #2: -> 'paketo-buildpacks/ruby@0.42.1' Step #2: -> 'paketo-buildpacks/bundle-install@0.8.1' Step #2: -> 'paketo-buildpacks/bundler@0.8.1' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.7' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.6' Step #2: -> 'paketo-buildpacks/image-labels@4.5.5' Step #2: -> 'paketo-buildpacks/mri@0.14.10' Step #2: -> 'paketo-buildpacks/node-engine@3.0.1' Step #2: -> 'paketo-buildpacks/passenger@0.13.3' Step #2: -> 'paketo-buildpacks/procfile@5.6.8' Step #2: -> 'paketo-buildpacks/puma@0.4.37' Step #2: -> 'paketo-buildpacks/rackup@0.4.36' Step #2: -> 'paketo-buildpacks/rails-assets@0.10.4' Step #2: -> 'paketo-buildpacks/rake@0.4.36' Step #2: -> 'paketo-buildpacks/thin@0.5.36' Step #2: -> 'paketo-buildpacks/unicorn@0.4.36' Step #2: -> 'paketo-buildpacks/yarn@1.2.0' Step #2: -> 'paketo-buildpacks/yarn-install@1.2.2' Step #2: -> 'paketo-buildpacks/web-servers@0.19.1' Step #2: -> 'paketo-buildpacks/ca-certificates@3.6.5' Step #2: -> 'paketo-buildpacks/environment-variables@4.5.5' Step #2: -> 'paketo-buildpacks/httpd@0.7.14' Step #2: -> 'paketo-buildpacks/image-labels@4.5.4' Step #2: -> 'paketo-buildpacks/nginx@0.15.6' Step #2: -> 'paketo-buildpacks/node-engine@2.0.0' Step #2: -> 'paketo-buildpacks/node-run-script@1.0.13' Step #2: -> 'paketo-buildpacks/npm-install@1.3.0' Step #2: -> 'paketo-buildpacks/procfile@5.6.6' Step #2: -> 'paketo-buildpacks/source-removal@0.2.1' Step #2: -> 'paketo-buildpacks/watchexec@2.8.5' Step #2: -> 'paketo-buildpacks/yarn@1.1.11' Step #2: -> 'paketo-buildpacks/yarn-install@1.2.1'
I suspect it is related to the pull policy changing but it could be other datadog related issues.
https://github.com/paketo-buildpacks/nodejs/compare/main%40%7B30day%7D...main#diff-c913eb03693bd44c528b2cad41d29db0a9faa3fef00b9498140cd31595c11f85R31
This seems DataDog related and since we removed the DataDog buildpack, closing. Please let us know if that was not the right thing to do.
I have a simple rails app and after upgrading to datadog 4x and nodejs@2.1.0 it pulls in too many buildpacks and fails
I rolled back the nodejs@2.0.0 and datadog@3.6.0 and that resolves the issue.
it suddenly pulled in
I suspect it is related to the pull policy changing but it could be other datadog related issues.
https://github.com/paketo-buildpacks/nodejs/compare/main%40%7B30day%7D...main#diff-c913eb03693bd44c528b2cad41d29db0a9faa3fef00b9498140cd31595c11f85R31