title: Perplexity
source: https://www.perplexity.ai/search/2cf6daa5-e002-4835-b3b9-1ad155b38608
author:
- "[[Perplexity AI]]"
published:
created: 2025-03-20
description: Perplexity is a free AI-powered answer engine that provides accurate, trusted, and real-time answers to any question.
tags:
- Docker
- Containers
[
how do i install portainer on port 9000 on garuda
[
Cherry Servers
How to Install Portainer on Ubuntu 22.04 - Cherry Servers
[
Atlantic.Net
How to Install Portainer Docker UI Web Interface on Debian
[
docs.portainer.io
Install Portainer CE with Docker on Linux
+3
sources
To install Portainer on port 9000 on Garuda Linux, follow these steps:
sudo pacman -Syu
sudo pacman -S docker
sudo systemctl start docker
sudo systemctl enable docker
docker volume create portainer_data
docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
http://localhost:9000
After installation, you'll be prompted to create an admin user when you first access the Portainer web interface. Follow the on-screen instructions to complete the setup12.
how do i install portainer-ce on port 9000 on garuda
how do i install portainer-ce on port 9000 on garuda
[
Linuxiac
How to Install and Use Portainer to Manage Docker Containers
[
Earthly Blog
Using Portainer with Docker and Docker Compose - Earthly Blog
[
My How-To on installing Portainer on Docker on Ubuntu Server 22.04 LTS with CIFS / SMB Shares as mounts for Docker Containers
My How-To on installing Portainer on Docker on Ubuntu Server ...
](https://www.reddit.com/r/selfhosted/comments/zffrsr/my_howto_on_installing_portainer_on_docker_on/)
+5
sources
To install Portainer CE on port 9000 on Garuda Linux, follow these steps:
sudo pacman -Syu
sudo pacman -S docker
sudo systemctl start docker
sudo systemctl enable docker
docker volume create portainer_data
docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
http://localhost:9000
After installation, you'll be prompted to create an admin user when you first access the Portainer web interface. Follow the on-screen instructions to complete the setup.
Note that while the latest versions of Portainer CE typically use port 9443 for HTTPS access, this installation specifically uses port 9000 for HTTP access as requested125.
sudo docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest [sudo] password for garyrust: Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. Error: short-name "portainer/portainer-ce:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"
You've reached your Pro limit
Upgrade to Perplexity Pro to increase your daily limit
sudo docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest [sudo] password for garyrust: Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. Error: short-name "portainer/portainer-ce:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"
[
podman-desktop.io
Managing Docker compatibility - Podman Desktop
[
Amit Bahree's (useless?) insight!
Podman error on Ubuntu - short-name did not resolve to an alias ...
[
TechRepublic
How to deploy the Portainer container manager with Podman
+16
sources
The error you're encountering is related to Podman's handling of short names for container images. To resolve this issue and install Portainer CE on port 9000 using Podman, follow these steps:
/etc/containers/registries.conf
file to allow unqualified image searches. Add the following lines to the file:sudo nano /etc/containers/registries.conf
Add these lines at the end of the file:
unqualified-search-registries = ["docker.io"]
sudo podman run -d -p 9000:9000 --name=portainer --restart=always -v /run/podman/podman.sock:/var/run/docker.sock:Z -v portainer_data:/data docker.io/portainer/portainer-ce:latest
sudo podman ps
http://localhost:9000
Replace "localhost" with your server's IP address if accessing remotely.
After installation, you'll be prompted to create an admin user when you first access the Portainer web interface. Follow the on-screen instructions to complete the setup36.
Note: The command uses /run/podman/podman.sock
instead of /var/run/docker.sock
because you're using Podman. The :Z
at the end of the volume mount ensures proper SELinux context3.
Related
How do I configure Podman to use the Docker socket
What are the steps to enable Docker compatibility in Podman
How can I resolve the short-name error in Podman
What are the necessary configurations for running Portainer with Podman
How do I set up Portainer to use Podman as the container engine
[
Home
[
Discover
[
Spaces
[
Library
[
how do i install portainer on port 9000 on garuda
[
on deploy on docker on mint linux: Failure container create: unable to find network with name or ID bridge: network not found
[
Error: Failed to create local member network "incusbr0" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.191.201.1: Address already in use")
[
I moved my pinokio directory to uuid 701b8caf-0a70-44a4-9f69-e374d1cc5496.. I want to mount that pinokio back into my /home/garyrust directory using fstab. How do I do it
[
libsqlite 3.49.0 has made a breaking change that breaks apps like stable-diffusion-webui or forge conda-forge/sqlite-feedstock#130 This is not a Pinokio bug, but anyone using a conda package that relies no libsqlite would have this issue (even if you manually install stuff without even using pinokio). As seen here lllyasviel/stable-diffusion-webui-forge#2669 and many other places. The fundamental fix should be for the conda sqlite maintainers to actually fix this broken release but since we can't wait, going to fix this so it works even when they don't fix it anytime soon. Fixed it by pinning sqlite at 3.47.2 How can I do this on MX23 Linux. Mine has sqlite version 3.40.1-2+deb12u1
[
Home
[
Discover
[
Spaces
[
Library
[
how do i install portainer on port 9000 on garuda
[
on deploy on docker on mint linux: Failure container create: unable to find network with name or ID bridge: network not found
[
Error: Failed to create local member network "incusbr0" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.191.201.1: Address already in use")
[
I moved my pinokio directory to uuid 701b8caf-0a70-44a4-9f69-e374d1cc5496.. I want to mount that pinokio back into my /home/garyrust directory using fstab. How do I do it
[
libsqlite 3.49.0 has made a breaking change that breaks apps like stable-diffusion-webui or forge conda-forge/sqlite-feedstock#130 This is not a Pinokio bug, but anyone using a conda package that relies no libsqlite would have this issue (even if you manually install stuff without even using pinokio). As seen here lllyasviel/stable-diffusion-webui-forge#2669 and many other places. The fundamental fix should be for the conda sqlite maintainers to actually fix this broken release but since we can't wait, going to fix this so it works even when they don't fix it anytime soon. Fixed it by pinning sqlite at 3.47.2 How can I do this on MX23 Linux. Mine has sqlite version 3.40.1-2+deb12u1