-
Notifications
You must be signed in to change notification settings - Fork 68
build error #42
Comments
Hi, it looks like cached docker layers are not working correctly for some reason (I can build this image without problems when docker cache is not used) - #43 PR should mitigate this issue. |
Thank you for your reply. |
Best way would be to simply update nauta's code to latest version (PR that I've mentioned above is already merged) and run the build again, nauta/rpm/python should work now |
I built nauta on bare-metal successfully, but I failed on Kubernetes pod, What can I do? or Is it impossible to build on kubernetes pod? error message partial --- Thank you, |
Could you tell me what particular image build is failing? If you mean that you want to build Nauta on some Kubernetes pod (like running |
Thank you for your reply, |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
I've got errors as below during building nauta on kubernetes pod system as build system.
---------------------------------------------------------------------------------------------
fatal: [local]: FAILED! => {"ansible_job_id": "452303190776.86355", "attempts": 5, "changed": false, "finished": 1, "msg": "Error building nauta/rpm/python - code: 127, message: The command '/bin/sh -c pip install -U pip==19.0.3 virtualenv==16.0.0 setuptools==39.2.0 wheel==0.31.1' returned a non-zero code: 127, logs: ['Step 1/12 : ARG BASE_IMAGE=shared/centos/rpm-packer', '\n', 'Step 2/12 : ARG PYTHON2_PIP_RPM_IMAGE=shared/build/rpm/python2-pip', '\n', 'Step 3/12 : FROM ${PYTHON2_PIP_RPM_IMAGE} as python2_pip_rpm_image', '\n', ' ---> 03175a7225d0\n', 'Step 4/12 : FROM ${BASE_IMAGE}', '\n', ' ---> 0cf01b1e3621\n', 'Step 5/12 : ENV RPM_VERSION=2.7', '\n', ' ---> Using cache\n', ' ---> 1a58dc8d7507\n', 'Step 6/12 : ENV RPM_RELEASE=0', '\n', ' ---> Using cache\n', ' ---> 54fe0479563b\n', 'Step 7/12 : RUN yum update -y && yum install -y python-devel python libffi-devel openssl-devel gcc gcc-c++', '\n', ' ---> Using cache\n', ' ---> d08159f4c7fb\n', 'Step 8/12 : RUN curl "https://bootstrap.pypa.io/get-pip.py" | python', '\n', ' ---> Using cache\n', ' ---> 753d99098bff\n', 'Step 9/12 : RUN pip install -U pip==19.0.3 virtualenv==16.0.0 setuptools==39.2.0 wheel==0.31.1', '\n', ' ---> Running in 7ca17da74ecf\n', '\x1b[91m/bin/sh: pip: command not found\n\x1b[0m', 'Removing intermediate container 7ca17da74ecf\n']"}
---------------------------------------------------------------------------------------------
This message say that pip command is not found, but pip command is exist.
Cluster configuration details:
I tried on my own system.
printf "$(uname -srm)\n$(cat /etc/os-release)\n"
):Linux 4.4.214-1.el7.elrepo.x86_64 x86_64
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
This system info about Docker container, actually k8s on nauta.
nctl version
)(git rev-parse --short HEAD
):git cloned today(2020/03/10)
Nauta component related with bug: (
build system/installer/nctl(cli)/dashboard/documentation/k8s/any of nauta container
)make k8s-installer-build
What is the current behavior?
What is the expected behavior?
Steps to reproduce:
*
*
Anything else do we need to know:
Is any problem building on container(actually nauta)
The text was updated successfully, but these errors were encountered: