Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.devcontainer errors on build with "failed to create symbolic link '/usr/bin/pip': File exists" #207

Closed
glennmusa opened this issue May 13, 2021 · 1 comment · Fixed by #208
Assignees
Labels
bug Something isn't working

Comments

@glennmusa
Copy link
Contributor

Description
Users cannot build a container with the .devcontainer

Steps to Reproduce
Steps to reproduce the behavior:

  1. clone the repo and re-open in container
  2. or create a codespace from main

Expected behavior
A container is built and you have the tools you need to develop

Actual behavior
The container fails to build, erroring out at this block: https://github.com/Azure/missionlz/blob/main/.devcontainer/Dockerfile#L28-L33

@glennmusa glennmusa added the bug Something isn't working label May 13, 2021
@sstjean sstjean self-assigned this May 13, 2021
@brooke-hamilton
Copy link
Contributor

Until we get a fix checked in, a workaround is to edit the Dockerfile to remove the line that creates a symbolic link for pip.

# Install Python 3
RUN apt-get update \
    && apt-get install -y \
    python3 \
    python3-pip \
    && ln -s /usr/bin/python3 /usr/bin/python
    # && ln -s /usr/bin/pip3 /usr/bin/pip --this line is removed because it causes a build error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants