GoogleContainerTools
stack smashing detected
Actual behavior
When installing the following dependencies via apt-get RUN apt-get update && apt-get install --assume-yes -o Dpkg::Options::="--force-confnew" libgl1-mesa-dev libglib2.0-0 the next call to pip in the Dockerfile will result in the following error:
INFO[0040] Running: [/bin/sh -c pip install --upgrade pip]
*** stack smashing detected ***: terminated
Aborted (core dumped)
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 134
This container builds cleanly on another Debian box
Expected behavior A clean build, with no stack smashing error
To Reproduce
FROM python:3.9.5
RUN apt-get update && apt-get install --assume-yes -o Dpkg::Options::="--force-confnew" libgl1-mesa-dev libglib2.0-0
RUN pip install --upgrade pip
Additional Information The above dockerfile should reproduce No context necessary to reproduce
kube executor config:
runners:
config: |
[[runners]]
executor = "kubernetes"
environment = [ "container=kube" ]
[runners.kubernetes]
namespace = "{{.Release.Namespace}}"
image = "ubuntu:16.04"
image_pull_secrets = [<SOME_SECRETS>]
[runners.cache]
Type = "s3"
Path = "runner"
Shared = true
[runners.cache.s3]
ServerAddress = "s3.amazonaws.com"
BucketName = "<BUCKET_NAME>"
BucketLocation = "us-east-1"
Insecure = false
Triage Notes for the Maintainers
| Description | Yes/No |
|---|---|
| Please check if this a new feature you are proposing |
|
| Please check if the build works in docker but not in kaniko |
|
Please check if this error is seen when you use --cache flag |
|
| Please check if your dockerfile is a multistage dockerfile |
|
@crohling I faced this problem. Do you have any idea to solve this issue?
@ardasendur I was never able to resolve it. My solution was to use raw docker.