You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cockpit-podman doesn't seem to be aware of the user service running so the "User Podman service is also available" banner is always displayed and none of the user-service specific options are available.
Cockpit itself seems to be aware of the service running:
And the output of systemctl seems to indicate that it is:
user@server:~$ systemctl --user status podman.socket
● podman.socket - Podman API Socket
Loaded: loaded (/usr/lib/systemd/user/podman.socket; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-08-26 09:22:50 UTC; 8min ago
Triggers: ● podman.service
Docs: man:podman-system-service(1)
Listen: /run/user/1000/podman/podman.sock (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/podman.socket
There aren't errors shown in the JS console or any logs that I'm aware of the location of.
When I click the "Start" button nothing happens and the banner remains however the output in the JS console is:
[Log] SyntaxError: JSON Parse error: Unexpected EOF (index.js, line 2)
parse
(anonymous function) — index.js:2:1457746
promiseReactionJob
[Log] re (cockpit.js, line 1)
message: "Unknown interface 'org.freedesktop.systemd1.Service'."
name: "org.freedesktop.DBus.Error.UnknownInterface"
problem: null
toString: function()
re Prototype
constructor: function(e,t)
Object Prototype
There aren't any particular steps to reproduce, this was a clean install of Ubuntu Server 20.04 that I had installed cockpit on (but not cockpit-podman) and then immediately updated to Ubuntu Server 21.04 and installed cockpit-podman on.
The text was updated successfully, but these errors were encountered:
Can you run curl --unix-socket /run/user/1000/podman/podman.sock http://d/v1.24/events and let it run and then in different terminal do some podman action (for example podman run). Do you see events coming in? Does it stay open indefinitely?
@marusak This was with 0 images and 0 containers set up, however even when adding containers I still had the error.
Interestingly I'd decided to go with Docker instead so had uninstalled podman and cockpit-podman completely (something I'd tried a few times to fix this anyway with little success) however, after re-installing it to test your suggestions it appears to be working correctly - I'm not sure if the Docker installation has maybe done something with permissions somewhere that has made it function correctly?
As for your debugging step with curl - that appears to be working as expected, which is expected I guess as cockpit-podman now seems to be working correctly too.
I'll close this issue for now as it's no longer an issue, if I come across it again I'll re-open it.
Cockpit version: 264-1
Cockpit-podman version: 45-1
Podman version: 3.4.4+ds1-1ubuntu1
OS: Ubuntu Server 22.04.1 LTS
cockpit-podman doesn't seem to be aware of the user service running so the "User Podman service is also available" banner is always displayed and none of the user-service specific options are available.
Cockpit itself seems to be aware of the service running:
And the output of
systemctl
seems to indicate that it is:There aren't errors shown in the JS console or any logs that I'm aware of the location of.
When I click the "Start" button nothing happens and the banner remains however the output in the JS console is:
There aren't any particular steps to reproduce, this was a clean install of Ubuntu Server 20.04 that I had installed
cockpit
on (but notcockpit-podman
) and then immediately updated to Ubuntu Server 21.04 and installedcockpit-podman
on.The text was updated successfully, but these errors were encountered: