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

UmbrelOS install on Debian fails [solution found, needs review] #1778

Closed
highghlow opened this issue Apr 1, 2024 · 5 comments · Fixed by #1780
Closed

UmbrelOS install on Debian fails [solution found, needs review] #1778

highghlow opened this issue Apr 1, 2024 · 5 comments · Fixed by #1780

Comments

@highghlow
Copy link
Contributor

OS: Debian x64, just installed + installed sudo and curl

The UmbrelOS installation script fails while trying to install some pip libraries. This is caused by an update in pip, that disallows installing any packages through it, to protect the system (keyword: externally-managed-environment). If this system is deactivated by removing /usr/lib/python3.11/EXTERNALLY-MANAGED pip errors out with AttributeError: cython_sources <...> error: subprocess-exited-with-error.

@highghlow
Copy link
Contributor Author

The issue seem to occur when installing docker-compose using pip in install_docker-compose. This package is packaged by Debian, so the code in this function could be replaced with

install_docker_compose() {
  sudo apt-get install --yes libffi-dev docker-compose
}

After this modification the installation succedes

@highghlow highghlow changed the title UmbrelOS install on Debian fails UmbrelOS install on Debian fails [solution found, needs review] Apr 1, 2024
This was referenced Apr 2, 2024
@Lexanger
Copy link

Lexanger commented Apr 2, 2024

Would a easier solution be to update the start script to use "docker compose" instead of docker-compose?

@highghlow
Copy link
Contributor Author

Would a easier solution be to update the start script to use "docker compose" instead of docker-compose?

In my experience, docker compose never worked. Maybe they changed something, but this doesn't change the underlying issue

@Lexanger
Copy link

Lexanger commented Apr 2, 2024

That’s interesting, I couldn’t get it to work with your changes but simply updating it to use docker compose worked instantly.

@highghlow
Copy link
Contributor Author

That’s interesting, I couldn’t get it to work with your changes but simply updating it to use docker compose worked instantly.

Maybe it tries to use the faulty python library when you call docker-compose, but uses the proper one when you call docker compose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants