Skip to content
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

podman failure due to strong regex filter (pull request attached) #104

Open
Alex-K37 opened this issue Nov 17, 2023 · 0 comments
Open

podman failure due to strong regex filter (pull request attached) #104

Alex-K37 opened this issue Nov 17, 2023 · 0 comments

Comments

@Alex-K37
Copy link

Alex-K37 commented Nov 17, 2023

[container@144 ~]$ CONTAINER_HOST=tcp://localhost:2375 podman container ls
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: ping response was 403
[container@144 ~]$ podman container logs -f dockerproxy2 
[WARNING] 320/134849 (1) : Can't open server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy dockerfrontend started.
[NOTICE] 320/134849 (1) : New worker #1 (2) forked
10.0.2.100:40466 [17/Nov/2023:13:48:58.158] dockerfrontend dockerfrontend/<NOSRV> 0/-1/-1/-1/0 403 189 - - PR-- 1/1/0/0/0 0/0 "GET /v4.6.1/libpod/_ping HTTP/1.1"

Cause: regex filter is too strong for podman.
Remedy: Pull request #113 adds an optional url level matching the libpod keyword (or any other keyword)

@Alex-K37 Alex-K37 changed the title podman failure due to strong regex filter podman failure due to strong regex filter (pull request attached) Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant