starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Docker VM - Repeating 'port X entered blocking/forward/disabled state' #1615

New Issue
Closed
opened 2026-02-05 01:46:14 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 01:46:14 +03:00
Owner
Copy Link

Originally created by @Furglitch on GitHub (Sep 12, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

docker-vm

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/docker-vm.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.4/39d8a4de7dfb2c40 (running kernel: 6.8.12-8-pve)

📝 Provide a clear and concise description of the issue.

Installation of the vm does not have any issues, but when starting containers, I get an output that is some variety of what's show below.

 [778.060112] br-74f3cb610d98: port 2(veth5264001) entered blocking state 
 [778.060708] br-74f3cb610d98: port 2(veth5264001) entered forwarding state 
 [778.061376] IPv6: ADDRCONF (NETDEV_CHANGE): br-74f3cb610d98: link becomes ready 
 [778.065066] br-74f3cb610d98: port 2(veth5264001) entered disabled state 
 [778.0939831 eth0: renamed from vethd70be08
 [778.107761] IPv6: ADDRCONF (NETDEV_CHANGE): veth5264001: link becomes ready 
 [778.1083901 br-74f3cb610d98: port 2(veth5264001) entered blocking state 
 [778.108988] br-74f3cb610d98: port 2(veth5264001) entered forwarding state

Depending on the container, this may show only when it starts (i.e. watchtower, hello-world) or constantly output (still trying to find the container that's doing this specifically).

Apologies if this is intended functionality, but I cannot for the life of me find how to disable this.

🔄 Steps to reproduce the issue.

  1. Install via script
  2. Start a container (either with docker compose or docker run)
  3. Monitor the terminal output

❌ Paste the full error output (if available).

Using my docker-compose file

root@docker:/mnt/hoard# docker compose -f /docker-compose/util/docker-compose.yaml up -d
[WARN] [0000] /mnt/hoard/docker-compose/util/docker-compose.yaml: the attribute 'version' is obsolete, it will be ignored, please remove it to avoid potential confusion
[-] Running 1/3
[+] Network util_default Created 0.1s
[+] Container deunhealth Starting 0.1s
[+] Container watchtower Starting 0.1s
[ 778.036025] br-74f3cb610d98: port 1(veth78c6b77) entered blocking state
[ 778.036080] br-74f3cb610d98: port 1(veth78c6b77) entered disabled state
[ 778.037521] device veth78c6b77 entered promiscuous mode
[ 778.042641] br-74f3cb610d98: port 1(veth78c6b77) entered blocking state
[ 778.042958] br-74f3cb610d98: port 1(veth78c6b77) entered forwarding state
[-] Running 1/3br-74f3cb610d98: port 1(veth78c6b77) entered disabled state
[+] Network util_default Created 0.1s
[+] Container deunhealth Starting 0.2s
[+] Container watchtower Starting 0.2s
[ 778.060112] br-74f3cb610d98: port 2(veth5264001) entered blocking state
[ 778.060708] br-74f3cb610d98: port 2(veth5264001) entered forwarding state
[ 778.061376] IPv6: ADDRCONF(NETDEV_CHANGE): br-74f3cb610d98: link becomes ready
[ 778.065066] br-74f3cb610d98: port 2(veth5264001) entered disabled state
[ 778.093983] eth0: renamed from wethdb2d70e08
[ 778.107761] IPv6: ADDRCONF(NETDEV_CHANGE): veth5264001: link becomes ready
[ 778.108390] br-74f3cb610d98: port 2(veth5264001) entered blocking state
[ 778.108988] br-74f3cb610d98: port 2(veth5264001) entered forwarding state
[+] Running 3/3eth0: renamed from wethdb2a7d1
[+] Network util_default Created 0.1s
[+] Container deunhealth Started 0.4s
[+] Container watchtower Started 0.4s
root@docker:/mnt/hoard#

Using hello-world image

root@docker:/mnt/hoard# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
17eec7bbc9d7: Pull complete
Digest: sha256:54e66cc1dd1fcb1c3c58bd8017914d8ed8701e2d8c74d9262e26bd9cc1642d31
Status: Downloaded newer image for hello-world:latest
[ 1625.185678] docker0: port 1(veth0f91593) entered blocking state
[ 1625.186302] docker0: port 1(veth0f91593) entered disabled state
[ 1625.186927] device veth0f91593 entered promiscuous mode
[ 1625.208250] eth0: renamed from vethc4e6a89
[ 1625.216340] IPv6: ADDRCONF(NETDEV_CHANGE): veth0f91593: link becomes ready
[ 1625.217000] docker0: port 1(veth0f91593) entered blocking state
[ 1625.217527] docker0: port 1(veth0f91593) entered forwarding state
[ 1625.218109] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
   (amd64)
3. The Docker daemon created a new container from that image which runs the
   executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
   to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
https://docs.docker.com/get-started/

[ 1625.274943] docker0: port 1(veth0f91593) entered disabled state
[ 1625.275922] vethc4e6a89: renamed from eth0
[ 1625.340268] docker0: port 1(veth0f91593) entered disabled state
[ 1625.342412] device veth0f91593 left promiscuous mode
[ 1625.343169] docker0: port 1(veth0f91593) entered disabled state
root@docker:/mnt/hoard#

🖼️ Additional context (optional).

Aside from adding SMB mountpoints to /etc/fstab, I have not made any additional changes to the vm.

This is the repo that I use to manage my docker stack
https://github.com/furglitch/docker-stack

Originally created by @Furglitch on GitHub (Sep 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? docker-vm ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/docker-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.4/39d8a4de7dfb2c40 (running kernel: 6.8.12-8-pve) ### 📝 Provide a clear and concise description of the issue. Installation of the vm does not have any issues, but when starting containers, I get an output that is some variety of what's show below. ```bash [778.060112] br-74f3cb610d98: port 2(veth5264001) entered blocking state [778.060708] br-74f3cb610d98: port 2(veth5264001) entered forwarding state [778.061376] IPv6: ADDRCONF (NETDEV_CHANGE): br-74f3cb610d98: link becomes ready [778.065066] br-74f3cb610d98: port 2(veth5264001) entered disabled state [778.0939831 eth0: renamed from vethd70be08 [778.107761] IPv6: ADDRCONF (NETDEV_CHANGE): veth5264001: link becomes ready [778.1083901 br-74f3cb610d98: port 2(veth5264001) entered blocking state [778.108988] br-74f3cb610d98: port 2(veth5264001) entered forwarding state ``` Depending on the container, this may show only when it starts (i.e. watchtower, hello-world) or constantly output (still trying to find the container that's doing this specifically). Apologies if this is intended functionality, but I cannot for the life of me find how to disable this. ### 🔄 Steps to reproduce the issue. 1. Install via script 2. Start a container (either with `docker compose` or `docker run`) 3. Monitor the terminal output ### ❌ Paste the full error output (if available). Using my docker-compose file ```bash root@docker:/mnt/hoard# docker compose -f /docker-compose/util/docker-compose.yaml up -d [WARN] [0000] /mnt/hoard/docker-compose/util/docker-compose.yaml: the attribute 'version' is obsolete, it will be ignored, please remove it to avoid potential confusion [-] Running 1/3 [+] Network util_default Created 0.1s [+] Container deunhealth Starting 0.1s [+] Container watchtower Starting 0.1s [ 778.036025] br-74f3cb610d98: port 1(veth78c6b77) entered blocking state [ 778.036080] br-74f3cb610d98: port 1(veth78c6b77) entered disabled state [ 778.037521] device veth78c6b77 entered promiscuous mode [ 778.042641] br-74f3cb610d98: port 1(veth78c6b77) entered blocking state [ 778.042958] br-74f3cb610d98: port 1(veth78c6b77) entered forwarding state [-] Running 1/3br-74f3cb610d98: port 1(veth78c6b77) entered disabled state [+] Network util_default Created 0.1s [+] Container deunhealth Starting 0.2s [+] Container watchtower Starting 0.2s [ 778.060112] br-74f3cb610d98: port 2(veth5264001) entered blocking state [ 778.060708] br-74f3cb610d98: port 2(veth5264001) entered forwarding state [ 778.061376] IPv6: ADDRCONF(NETDEV_CHANGE): br-74f3cb610d98: link becomes ready [ 778.065066] br-74f3cb610d98: port 2(veth5264001) entered disabled state [ 778.093983] eth0: renamed from wethdb2d70e08 [ 778.107761] IPv6: ADDRCONF(NETDEV_CHANGE): veth5264001: link becomes ready [ 778.108390] br-74f3cb610d98: port 2(veth5264001) entered blocking state [ 778.108988] br-74f3cb610d98: port 2(veth5264001) entered forwarding state [+] Running 3/3eth0: renamed from wethdb2a7d1 [+] Network util_default Created 0.1s [+] Container deunhealth Started 0.4s [+] Container watchtower Started 0.4s root@docker:/mnt/hoard# ``` Using hello-world image ```bash root@docker:/mnt/hoard# docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 17eec7bbc9d7: Pull complete Digest: sha256:54e66cc1dd1fcb1c3c58bd8017914d8ed8701e2d8c74d9262e26bd9cc1642d31 Status: Downloaded newer image for hello-world:latest [ 1625.185678] docker0: port 1(veth0f91593) entered blocking state [ 1625.186302] docker0: port 1(veth0f91593) entered disabled state [ 1625.186927] device veth0f91593 entered promiscuous mode [ 1625.208250] eth0: renamed from vethc4e6a89 [ 1625.216340] IPv6: ADDRCONF(NETDEV_CHANGE): veth0f91593: link becomes ready [ 1625.217000] docker0: port 1(veth0f91593) entered blocking state [ 1625.217527] docker0: port 1(veth0f91593) entered forwarding state [ 1625.218109] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ [ 1625.274943] docker0: port 1(veth0f91593) entered disabled state [ 1625.275922] vethc4e6a89: renamed from eth0 [ 1625.340268] docker0: port 1(veth0f91593) entered disabled state [ 1625.342412] device veth0f91593 left promiscuous mode [ 1625.343169] docker0: port 1(veth0f91593) entered disabled state root@docker:/mnt/hoard# ``` ### 🖼️ Additional context (optional). Aside from adding SMB mountpoints to /etc/fstab, I have not made any additional changes to the vm. This is the repo that I use to manage my docker stack https://github.com/furglitch/docker-stack
OVERLORD added the bug label 2026-02-05 01:46:14 +03:00
OVERLORD commented 2026-02-05 01:46:19 +03:00
Author
Owner
Copy Link

@Furglitch commented on GitHub (Sep 12, 2025):

Apologies, looks like this is a host issue, not a vm or script issue

Leaving this here for others, jic
https://forum.proxmox.com/threads/vmbr0-entered-blocking-state-then-disabled-then-blocking-then-forwarding.124934/

@Furglitch commented on GitHub (Sep 12, 2025): Apologies, looks like this is a host issue, not a vm or script issue Leaving this here for others, jic https://forum.proxmox.com/threads/vmbr0-entered-blocking-state-then-disabled-then-blocking-then-forwarding.124934/
OVERLORD commented 2026-02-05 01:46:22 +03:00
Author
Owner
Copy Link

@uSlackr commented on GitHub (Sep 16, 2025):

@Furglitch care to explain which of the possible issues fixed your install?
My issue is not only this but portainer_agent is throwing an error "is docker daemon running" when running as root. I fixed it by creating a user and running as non-root.

@uSlackr commented on GitHub (Sep 16, 2025): @Furglitch care to explain which of the possible issues fixed your install? My issue is not only this but portainer_agent is throwing an error "is docker daemon running" when running as root. I fixed it by creating a user and running as non-root.
OVERLORD commented 2026-02-05 01:46:26 +03:00
Author
Owner
Copy Link

@Furglitch commented on GitHub (Sep 16, 2025):

@Furglitch care to explain which of the possible issues fixed your install?

My ultimate resolution was switching away from the community scripts entirely, as I was struggling to get things working for my use. (samba shares, etc)
I swapped to a minimal archlinux install, and I am using a non-root user on that, so that may also play a factor

@Furglitch commented on GitHub (Sep 16, 2025): > @Furglitch care to explain which of the possible issues fixed your install? My ultimate resolution was switching away from the community scripts entirely, as I was struggling to get things working for my use. (samba shares, etc) I swapped to a minimal archlinux install, and I *am* using a non-root user on that, so that may also play a factor
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1615
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?