-
Notifications
You must be signed in to change notification settings - Fork 55
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
Install Redis Stack on Linux command doesn't work on Debian11 #112
Comments
I can confirm. Following the docs doesn't work for debian. |
I still cant install it on Ubuntu version 22 |
Hi, I'm in the process of documenting this. but please try these instructions: From Download, get the latest Stack snap package. To install, run:
|
Hi @nermiller! I tried the install with snap on a fresh ubuntu server, but after manually launching redis-stack-server, I get a bunch of errors:
I also tried Debian, Redhat and others versions of Ubuntu and it seems like at this point, there is no simple way to install redis-stack and run it. Is there any distribution you can recommend where it is that simple to install? I want to install it on a fresh server and distribution doesn't really matter to me. |
Thanks, @Vincz. I'll let the team know. We'll fix this ASAP. |
Hi @nermiller. Thank you for the reply. Unfortunately, Docker is not an option for me at the moment. |
Thanks in advance for your patience. I'll keep you posted. |
Is there any update on this? |
Isn't it possible to have exactly the same packages as Redis itself but with redis-stack instead? At the end of the day, redis-stack is just redis & module, isn't it? |
@Vincz - does this still happen? I just removed all of the dockers on my system, and cold started everything on a debian:11 (bullseye) docker. This is literally what I did - to pull down the packages (for a new new docker) so YMMV.
Previously, I had a gpg key mismatch error, with they key imported. But it appears to have resolved itself. |
Tried with yours, still no luck. |
@akashbit What's your docker image or debian situation? The current hash of the latest bullseye image is 446440c01886, and that ran fine. Do you have lsb-release installed? Mind sharing the output? |
doing it on ubuntu22.04 ... followed exactly your guide. not docker. |
Ah- I see, this issue is a mix. I've since split the Ubuntu 22.04 issue into #126. This one focuses on Debian11. As for the Ubuntu issue, I think I have a lead on that. It appears that packages can no longer be in repositories, using the old x86_64 platform. Starting with Jammy it appears that Ubuntu no longer auto translates that to amd64. So... I'm making changes. Hopefully this closes shortly. |
thanks @chayim |
Any time :D |
Any updates on this one? Neither the package
This effectively means, we cannot build our custom Debian derived docker image with redis stack. (Due to policies, the official image is not an option 😢 ) |
Any update ? |
Any update, please? |
I'm on Debian on WSL and still get the same error, does anyone foud a solution ? |
Follow the official instruction https://redis.io/docs/latest/operate/oss_and_stack/install/install-stack/linux and got error message Unable to locate package redis-stack-server on Ubuntu Server 24.04 Then tried the same on Ubuntu Server 22.04 LTS and the installation is success 😊 |
@manastunga787 because they not have any build for Ubuntu 24.04 I create PR for this redis-stack/redis-stack#566 |
This Appears to be the issue still in 2024 August. More than a year has passed but no fix? |
Any update on this ? |
I'm using Ubuntu24 and had the same "Unable to locate package redis-stack-server" error, but I managed to install it using snap. I assume if you're willing to install/use snap on Debian it might work on that too. I followed these instructions: https://redis.io/docs/latest/operate/oss_and_stack/install/install-stack/linux/#on-ubuntu-with-snap Now...if only I can figure out how to configure it... |
Following the instructions in https://redis.io/docs/stack/get-started/install/linux/
the package cannot be found
The text was updated successfully, but these errors were encountered: