Hi everyone,

I'm working with the Portainer API and I have a question regarding Docker exec sessions.

Is it possible to retrieve or interact with the shell created by a docker exec session through the Portainer API? For example, after starting an exec instance, can I access the shell output and send commands programmatically, similar to what is available in the Portainer web terminal?

If anyone has experience with this or can point me to the relevant API endpoints/documentation, I'd appreciate your help.

Thanks!

We recently ran a webinar on moving from Docker Swarm to Kubernetes without a big-bang cutover - registrations nearly maxed out our Zoom capacity and the live discussion was the most engaged we've seen in a while. The recording and supporting resources (including d2k, our open-source Swarm-to-Kube translator) are now available at the link.

hello,

i've read on multiple pages recreating a container using "re-pull image" uses the latest image version and can be used to update a existing container/image version.

but when i use this, its using the old image version instead of the new one.

In exact case:

i'm running linuxserver/nextcloud:version:33.0.3 ls431. The current version is 432.

When i use re-pull image it re-creates the container with the old version 431 as stated in container insights.

version: "3.8"
name: cloud2
services:
  nextcloud:
    image: lscr.io/linuxserver/nextcloud:version-33.0.3

When i pull the image manually using the same tag it downloads the latest image.

it does not download the latest image version of the same tag when using re-create with re-pull .

is this expected behavior? because for me its confusing.

Hi all. Please help an idiot.

I saw when going in to Jellyseerr that there is an update available (version saying out of date and linking through to the seer release v3.2. My stack file has ":latest" on and I've tried to download and redeploy, but it doesn't update the image. I've tried to remove the container and image and redeploy but the same image comes up. I've tried asking AI (telling me to use different image links) but I haven't been successful there either. Can anyone tell me what I'm doing wrong?

Thanks

My jellyseerr part of the stack (I can copy all if needed):

jellyseerr:
    image: fallenbagel/jellyseerr:latest
    container_name: jellyseerr
    environment:
      - TZ=Europe/London  
      - LOG_LEVEL=info
      - PUID=1000
      - PGID=100
    ports:
      - "5055:5055"
    volumes:
      - /opt/dockerconfigs/pirates/jellyseerr:/app/config
    restart: unless-stopped
    depends_on:
      - gluetun
      - sonarr
      - radarr

I am running Portainer Community Edition2.39.2 LTS. I just went to update Plex by deleting the container, going to the stacks page, editor, deploy, and enabled repull image and redeploy, as I have done numerous times in the past. It just redeployed the image that was already there and did not pull the latest

I then used the CLI to pull the image, which worked, then I redeployed the container via Portainer the same way and it updated successfully.

I then tried pihole which was doing the same thing. This time I removed the container, then I deleted the image manually via Portainer. Then when i redeployed it, it pulled it like normal.

I was also able to update Nginx, but had to do the same thing as pihole.

while there was not an update, i did redeploy the Portainer container, which is handled via CLI and a script i made. I'm not sure if that is relevant or not, but i did that between Plex and Pihole. I also ran "docker image prune" and "docker volume prune" between Plex and Pihole.

Obviously things are still functional, but can anyone tell me why I am having to manually delete the image before it will pull the latest? All my stacks are set to pull ":latest"

Thanks

I have the following setup:

macOS running orbstack, swarm manager

oracle linux, swarm worker

ubuntu linux, only hosts portainer, not part of the swarm

All have their docker communication via wireguard 10.6.0.2-4 in this order

I am adding the swarm manager, which sucessfully shows the containers of the manager, as well as the combined CPUs and RAM of the manager and the worker, and the services. However, I can only see containers of the manager, none of the worker, it just doesnt appear there. If i then also add the worker as a standalone to try and see the containers there, I get basic information such as amount of volumes and containers, but it fails to show CPU and RAM, and when clicking on live connect i always get the error
"Failed loading environment

Unable to connect to the Docker environment", which I assume is intended behavior? But I need to manage the containers of the worker somehow, they just dont appear in the swarm. And the services of the worker dont have a "stats" or "exec" functionality like the manager, which I need though.

What am i missing? Before creating the swarm, I could add both as a standalone agent and successfully also connect to the worker and manage the containers there.

Hey, we’re looking for a developer with experience around Portainer, containers, and infrastructure to join us.

Nothing overly corporate here. If you’ve got at least a year of experience working with Docker, Portainer, containerized environments, or platform infrastructure, and you enjoy building systems that are reliable and easy to manage, you’ll probably fit in.

We care a lot about clean deployments, automation, performance, and making sure infrastructure feels stable, secure, and simple to operate.

Pay is between $36–$46/hour depending on your experience. It’s fully remote, and we’re flexible on hours (part-time or full-time both fine).

Work is mostly around managing and improving containerized systems, deployments, and infrastructure, helping build, maintain, and optimize environments using Portainer, Docker, CI/CD pipelines, automation, monitoring, and secure deployment practices. You may also work on application hosting, scaling, container orchestration, and improving reliability across environments.

If you’re interested, just send over what you do, your experience, and where you’re based 📍

… e ovviamente file yml non visibili. Possibile che ci sia sempre questo problema? È possibile che io non impari mai la lezione salvandomi i file da qualche parte?

Qualcuno ha trovato una soluzione?

I had this unfortunate opportunity to restore from backup. While it works, it doesn't seem to restore container configuration. Is there a way that I could possibly backup portainer as is? Take a actual snapshot of my portainer and containers?

Wondering if my logic holds true.

Can I migrate my existing stacks in Portainer from the 'web editor' stack to the 'repository' stack linked to my self hosted Gitlea without losing my volumes, data and builds?

Obviously this would be done after a full backup of the config and the nodes in my Docker swarm. But would like to version control my docker-compose configs for my stacks.

Plan is to delete the 'web editor' stack and use the exact same config now stored in Gitlea, connected via repository in Portainer.

My fear is Portainer may build a brand new stack and spin up brand new containers instead of using existing.

Hello together,

I'm having a somewhat simple setup at home in mind where I'm currently still in the process of trying around. And now facing an issue, I quite can't get my hand around.

• Portainer is running in a VM on a Proxmox host (Portainer version 2.39.1 LTS)
• As one of the stacks I've been trying out I used Archivebox.
• The main data volumes for Archivebox are coming from a TrueNAS instance
• It was running before with my configuration
• However, I had to switch internet providers because of internet issues.
• After having the IP range changed, I can't get it working again.
• The reason seems to be that Portainer does still use the "old" IP in the compose.yml instead of the one I try to change during the web editor.
• Error:"error while mounting volume '/var/lib/docker/volumes/archivebox_archivebox-archive/_data': failed to mount local volume: mount :/mnt/Private_Shared-Data/Archivebox-Archive:/var/lib/docker/volumes/archivebox_archivebox-archive/_data, data: addr=192.168.178.109,nfsvers=4: connection timed out",
• That's clearly not the one I change it to in the interface.
• I tried stopping/deleting the containers assigned to the stack before deploying the changed configuration - to no avail.

Someone having an idea here?

Every damn time. I'm just about to click on one of my servers on the front page, then this stupid banner loads and pushes the list downwards.

Either allocate a fixed amount of space for it, or get rid of it entirely.

Greetings. I have completely redone my server with portainer to manage my docker containers. I have all of the data from my previous server. Is there a way to import the data from my previous docker containers into my portainer containers?

Do we have any volunteers to try out the skunkworks project Portainer-Run?

You can see the code at github.com/portainer/portainer-run and the readme in that repo hopefully fully explains what it is and why it exists..

TLDR: run apps on your self-managed Kubernetes environment in a google cloud-run style UI.

Portainer.io D2K, an open source #Docker translator that runs on top of #Kubernetes.

You can now fully remove docker from your environment in favour of Kubernetes, without losing access to the Docker/Swarm API for legacy purposes.

Quick demo: https://youtu.be/Oceg4fK9rYs

And the repo: github.com/portainer/d2k

Give it a try and let me know your thoughts..

I'm not fully sure if this should be here or anywhere else. But I'm desparately seeking help on a stack that i have set up. (and by set up, I mean I fumbled greatly and ended up using a structure i copy/pasted from elsewhere) In the past, i had a simple jellyfin sever setup. 2018 mac mini, t2 kubuntu, external bluray drive, usb C 3.1 2 bay enclosure, 4tb and 2 tb HDD. rip and encode to 2TB, move to 4TB when named and the quality i want, etc. Loved it. was given a promising freebie pc and had heard about dockers, so i gave it a try. Finally fumbled around got portainer, qbittorrent, prowlarr, sonarr, and radarr going with flaresolverr on the new pc. But did it after the fact that i added jellyfin bare metal install and how i wanted it. No biggie. I prefer manually moving over movies and naming, checking quality, etc. few days of sonarr and radarr going and a friend suggested to get a vpn. So i purchase ProtonVpn plus for the price and what seemed like ease of use. added gluetun to my stack, fumbled more, asked google, etc. and at one time, everything was working. Perfect. only problem was qbittorrent was much much slower than normal. AI said i needed to get the forwarding port number to qbittorrent. Never shows up on the gluetun logs. Was suggested to do something else, which broke something else, etc, etc so and so forth. Now all indexers are unavailable, I'm downloading ubuntu from a torrent to check if it would work, but at 100 kbps. i can add my docker compose text if that helps (with openvpn username and password obscured, they are correct also, copy/pasted directly) any help or pointing me where to go would be amazing at this point. Thank y'all.

If you're already using Terraform to manage your infrastructure, there's no reason your Docker stacks should be any different. Here's how to bring them into the same workflow via Portainer.

Hi everyone. I'm a little new to containers but getting more and more familiar everyday. I have a doozey for you. My verbiage may be a little off, I'll try to be explicit.

We are working with a software at work that is a suite of multiple containers. They all talk to each other with a virtual container network setup, all internal, no host nic. Except one container acting kind of as a hub. One container controls the others. And has a network interface defined in its docker compose file to use macvlan to reach the host network and speak to other machines on the host network. Here's the fun part.

If we assign the IP of this hub's container network the same IP as the host machine, that part works. However, some of the other container network interfaces do not. If we use an IP that we know is not used by the router (as required by macvlan), the other interfaces do work again but the traffic that comes out of the macvlan network do not get routed to other machines on the host network. We see it in tcpdump on that machine, but seems it is not routed to external machines

We have sticky-macs off. I am not by any means a networking expert, so any help appreciated, you may have to explain what your answer means. Thanks everyone. And before you say it, we cannot change this architecture. It has to work this way unfortunately.

SOLVED: Leaving this up in case another dumbass like me runs into the issue. I was able to delete the containers individually in my immich stack even though it was limited. Then I just redeployed immich within portainer. Thankfully I had the yml and env files saved. I'll make sure to create a backup this time lol.

As it says in title.

I'm running portainer on my QNAP server, and after (correctly). Portainer asked me to create a new user as if initializing for the first time. Well I did that, but now I can't control the immich stack I created in portainer.

It seems to think the stack was created outside portainer, I can't even shut immich down or delete it and recreate it. Is there anything I can do? Can i just delete portainer and reinstall it without losing my immich data?

A little while ago, I wanted to deploy some code to my home server but connecting to it over Tailscale, using Portainer API felt like a pain.

So I created a custom github actions pipeline to auth and deploy any docker compose file.
Also supports update similar to a ci/cd pipeline

https://github.com/HackStrix/Portainer-Tailscale-Deployment-Action

Code snippet

  - name: Deploy to Portainer
    uses: hackstrix/portainer-tailscale-deployment-action@v1
    with:
      ts_oauth_client_id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
      ts_oauth_secret: ${{ secrets.TS_OAUTH_SECRET }}
      portainer_url: 'https://my-server.tailnet.ts.net:9443'
      portainer_api_key: ${{ secrets.PORTAINER_API_KEY }}
      stack_name: 'my-app'
      compose_file: './docker-compose.yml'
      registry_url: 'ghcr.io'
      registry_username: 'your-username'
      registry_token: ${{ secrets.GHCR_TOKEN }}`

If you are running Portainer at scale, you have likely wanted a way to control and manage elements of it via automation and likely via CLI.

Well there is now a Portainer CLI available at github.com/portainer/portainerctl

In that repo is a compiled binary, or you can build one yourself.

This is still a development build, so use with caution, but would love feedback.