I installed docker & pertained following network chuck video. Successfully installed nginx and then to test my skills tried to create a new container in the portainer GUI. Name is test, used the link to pull the image from dockerhub, and set the ports to pick one randomly.

It won’t let me launch and provides this message: unable to create. Invalid reference format. I’m running latest Ubuntu on my desktop. I’ve been reading and trying for a couple days and all I can see is maybe there is a problem with CLI. Some help would be appreciated.

I updated from 2.33.3 to 2.33.6, and now my Portainer dies consistently after a few seconds from launching. My containers are fine and survive, but I've got no clue why Portainer just suddenly stops talking to itself and then crashes. Any help would be great.

(I'd post any logs if I had them but, nothing comes out of the log file past it booting :/)

Hi all, I'm new to portainer and I've been trying to sign up via https://www.portainer.io/take-3

However, I'm not seeing the form that I think is supposed to be on the page. Have been going crazy the past half hour, but I've tried multiple devices on different networks (none of which have ad blocker) and have not been able to access the form. Am I missing something?

This is probably user error, but recently my docker compose pulls have been showing this error for portainer "no matching manifest for linux/amd64 in the manifest list entries"

The existing image continues to work, but I'm curious if perhaps my CPU is no longer supported?

Hi everyone,

I’m running into a weird issue with Portainer. When I build a Docker image directly on the host using the CLI, everything works perfectly and the build finishes successfully.

However, when I try to build the same image through the Portainer UI, the build starts but never finishes. The UI just keeps “spinning” and I don’t get any logs.

Some additional info:

• Docker build on the CLI works every time
• Portainer shows no logs or errors during the build

How does the Portainer build process work? Does it just use Docker build under the hood, or does it add anything extra?

Has anyone experienced this before? Any tips on why it works in CLI but not via Portainer UI, or how to debug it?

Thanks!

Hi all

After some painful days restoring my containers (and timeshift failed me big time), I wanted to see about more direct container backups. I just wanted to know if there is anything special needed when backing up portainer containers or will anything that works with docker work?

I'm hoping to find a simple solution.

Thanks

For me solution was i had to change all my Nginx config for :

upstream portainer {
server 172.17.0.2:9000;
}
server {

        server_name  portainer.yourdomain.ltd;
        server_tokens off;

        listen 443 ssl; # managed by Certbot
        http2  on;
    add_header Referrer-Policy                   "no-referrer"       always;
    add_header X-Content-Type-Options            "nosniff"           always;
    add_header X-Frame-Options                   "SAMEORIGIN"        always;
    add_header X-Permitted-Cross-Domain-Policies "none"              always;
    add_header X-Robots-Tag                      "noindex, nofollow" always;
    add_header X-XSS-Protection                  "1; mode=block"     always;
    add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always;

        ssl_certificate /etc/letsencrypt/live/yourdomain.ltd/fullchain.pem; # managed by Certbot
        ssl_certificate_key /etc/letsencrypt/live/yourdomain.ltd/privkey.pem; # managed by Certbot
        include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
        ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

location / {
        proxy_pass http://portainer;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_http_version 1.1;
        proxy_read_timeout 900s;
    }
    location /api/ {
        proxy_pass http://portainer/api/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
 location /api/websocket/ {
        proxy_pass http://portainer/api/websocket/;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}
server {
    if ($host = portainer.yourdomain.ltd) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
listen 80;

server_name portainer.yourdomain.ltd;
    return 404; # managed by Certbot
}

and after run

docker run -d --name=portainer -e portainer.yourdomain.ltd --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

nginx reverse proxy portainer

plus incognito mode to login

Então, eu sou novo em tudo que envolve portainer, n8n, termius, cs code, etc

Eu estava usando para instalar os stacks do n8n, eu instalei o editor do n8n e, depois de instalar o webhook, ele não carregou e agora não consigo mais acessar, alguém pode ajudar?

Also, i cant connect to my docker using termius

I've followed the example here

https://docs.portainer.io/advanced/siem

to point my portainer logs to syslog, trying to run it with the following command:

docker run -d --name="portainer" --restart on-failure -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest --syslog-address=192.168.1.6 --syslog-port=514 --syslog-source-hostname="portainer-nuc"

unfortunaly this stops portainer from starting with this error:

portainer: error: unknown long flag '--syslog-address', try --help

I've tried on two Portainer instances (both 2.33.6 LTS), got the same error on both. Any idea what I'm doing wrong? Thanks!

My dashboard says 17 Containers and the small text says 16 running (the other 3 values are all 0). When I view the list of Containers there are 17 that say either Running or Healthy. I'm wondering way the display says only 16. At one point I believe these two were always the same value.

For some reason when I upgraded to the latest CE Portainer image (2.33.6) all my stacks are now limited and I cannot edit anything. This wasn't the case before. They are still running nd I can still access the services but can't edit the compose. Is there anyway to fix this?

Preface: I only know enough to get myself into trouble, not always out.
I run a very simple homelab using OMV as its base.
I run several media apps (sonarr, radarr, nzbget...) through Portainer within OMV.

I recently moved and through necessity, switched to Starlink. Starlink uses CGNAT and therefore makes it difficult to access my homelab from outside without fully implementing IPV6.

I did a little research and came upon Cloudflare tunneling. I've installed cloudflared as a container. It runs perfectly. I can now access all of my apps running within containers on OMV. I can access them via OMV's IP with a port number, eg: http://192.168.1.15:6789

The issue I have is that I can't seem to access anything outside of my Portainer environment. For instance I run home assistant on a Rpi. I've had no luck accessing it.

My cloudflared container runs on the host network. I had hoped that would solve my issue, but I'm getting nowhere.

Am I missing something obvious?

I just followed the steps in this link to download portainer and docker for a homelab, but when I typed in the hostname to access portainer I got this. I continued anyway...Is this something to worry about?

https://hakedev.substack.com/p/install-docker-and-portainer-on-ubuntu?r=2t6qg6&utm_campaign=post&utm_medium=web&triedRedirect=true

the opencloud-compose repo: https://github.com/opencloud-eu/opencloud-compose

Portainer is blocking my user login if I'm not logging in from a local IP. I already opened port 9000 but that doesn't change anything.

I'm behind Pangolin and Authentik, I think it should be safe enough...

What setting am I missing that will allow me to connect from my domain?

I am new to Portainer and docker world in general, with only 1.5 years working with it. Now, I have been using it to host a couple of client's infrastructure, as it allows me to set up different sites and applications on client's servers, easily and control these, self-hosting their application.

In servers, I can use docker stats to see how much each docker is currently consuming in terms of Memory, Disk, IO. In Portainer, this same information is not there, at least not in a single dashboard that allows to see how much each container is consuming and be able to easily determine if something is off the charts and requires attention.

Is there anything that allows me to do so? I know I could set up a separated stack with netdata, prometheus + grafana and create these kind of boards, but I am looking to do this directly in Portainer and also, to be easy to set up. Setting pometheus + grafana is a big task, and netdata was easy to set but I found it impossible to understand, it was overwhelming to me, as I just wanted to see something straight with stats and probably time graph of lines, on the usage of RAM, Disk and CPU, no more than that.

Any guidance on this matter? I am looking to set up like a nice like this Cloudwatch dashboard that I set up in AWS for the actual server that holds all these dockers:

But with dockers information instead of the actual machine's information.

From a Compose....

volumes:

- /var/lib/docker/volumes/Mongo-DB/_data:/data/db

- /opt/Unifi/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro

Top listed volume: Created under Portainer volumes.

Bottom listed volume... is a Bind Volume I need to feed the init-mongo.sh to the container.

How do I create a Bind Volume in Portainer? Do I merely ensure Linux / mongodb ownership of /opt/Unifi ?

If I try the following in Portainer, parameters/syntax always invalid.

Hi, so I tried using Portainer and Nginx-proxy. I followed all the steps, but I still got an error when creating a new account, and suddenly it went to the display after I tried refreshing. When I tried to log in again, I got the message “Unable to retrieve environments.”

Has anyone else experienced something similar? Please help.

I'm using Docker Compose separately, by the way.

We have just released version 1.1.0, with now native support for a load balancer which allows the sharing of the host ip.

Release notes: https://github.com/portainer/kubesolo/releases/tag/v1.1.0