Title
#tech-support
Alexsander Pereira

Alexsander Pereira

10/18/2022, 11:53 PM
Hello, can someone help me with this problem in the build?
11:57 PM
logs:
#9 [5/5] RUN echo '1765b89b-67b0-4ebf-beb4-8e086b3e3ad0' | sudo tee /orchest/task_1765b89b-67b0-4ebf-beb4-8e086b3e3ad0.txt
#9 0.410 /bin/sh: 1: sudo: not found
#9 ERROR: executor failed running [/bin/sh -c echo '1765b89b-67b0-4ebf-beb4-8e086b3e3ad0' | sudo tee /orchest/task_1765b89b-67b0-4ebf-beb4-8e086b3e3ad0.txt]: exit code: 127
------
 > [5/5] RUN echo '1765b89b-67b0-4ebf-beb4-8e086b3e3ad0' | sudo tee /orchest/task_1765b89b-67b0-4ebf-beb4-8e086b3e3ad0.txt:
#9 0.410 /bin/sh: 1: sudo: not found
------
ERROR: failed to solve: executor failed running [/bin/sh -c echo '1765b89b-67b0-4ebf-beb4-8e086b3e3ad0' | sudo tee /orchest/task_1765b89b-67b0-4ebf-beb4-8e086b3e3ad0.txt]: exit code: 127
11:57 PM
Using custom image: python:3.8
Rick Lamers

Rick Lamers

10/19/2022, 7:05 AM
Our image build process depends on
sudo
being available in the environment container image. I think you should be able to fix this by either: 1) Installing
sudo
in your environment setup script 2) Making sure your base image already has it included (wrapping your custom base image) If you're using a custom base image to change the Python version what would be an easier option is to use this example to change the Python version of the Orchest base image: https://docs.orchest.io/en/stable/fundamentals/environments.html#using-a-different-python-version Using custom base images is supported but to get everything to work properly with it can be quite complicated (e.g. making kernels work, making the Orchest SDK work).