Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

Several requests have been received via Twitter, IRC, email, and other sources, to provide a Podman Desktop application similar to the one that Docker provides.

This Desktop application should look and feel the same as much as possible across all three environments and should provide the ability to run Podman on the host it resides upon. For first-pass versions of Podman Desktop, it may be acceptable to run Podman on a specified Linux host, while running the Desktop on another host, whether it be Linux, macOS or Windows.

We plan to talk further about this at the Thursday September 16, 2021, Podman Community Cabal meeting at 10:00 a.m. EDT (UTC-4) Video Conference. The meeting is open to all and is free to attend.

If you have further requests or ideas for this part of the project, please feel free to reply to this issue and/or attend the meeting. I will reply to this issue with further updates as they arise.

Is your enhancement related to a problem? Please describe

Flatpak documentation for running Podman Desktop needs to say that it requires

systemctl --user start podman.socket

in order to run. No modifications to the Flatpak itself need to happen since it seems to pick up the Containers and Images after quitting the application and restarting it.

I was also unable to make the change to the flatpak by doing:

flatpak override --filesystem=/run/user/1000/podman/podman.sock io.podman_desktop.PodmanDesktop

I got permissions denied, but Flatseal seemed to do the trick.

Describe the solution you'd like

State that users will need the Podman Socket enabled.

systemctl --user enable podman.socket
systemctl --user start podman.socket

Describe alternatives you've considered

No response

Additional context

No response

UI - add feature : #156

make registries editable

https://user-images.githubusercontent.com/58530461/173376189-b06de357-311b-4921-a13c-ac84cbc84e1f.mp4

HOW I DID IT? basic idea: delete the old registry create a new registry, using the old registry and the changed data.

• create a new component PreferncesEditRegistrieModal.svelte
• used the same logic as PreferencesRegistriesCreateRegistryModal.svelte why did i not used the same component? as it was looking more complicated to do! and had to add more rendering logic in the html part.

PROBLEMS?

• only when you change the URL in edit, it create a new registry, and dose not delete the old one.

Please let me know any changes you world like

Bug description

For some reason, containers don't show up in the list, although there are currently several containers running on the system using Podman. I think this happened after I did a prune on containers in the terminal. Nevertheless, there are running containers, but none is currently shown. Switched to latest development version. It didn't help.

Operating system

Fedora 36

Version

next (development version)

Steps to reproduce

• Open Podman Desktop
• Make sure you have a few containers
• Check the containers list

Relevant log output

No response

Additional context

No response

Bug description

I have a working podman installation on Oracle Linux. I just installed podman-desktop via flatpak. On launch the home screen displays the 'Podman is Running' message. When I run any container via the podman command line they start up correctly, but none are listed in the podman-desktop application and it displays 'No Container Engine | Configure/Start a container engine first'

Operating system

Oracle Linux Server release 8.6

Version

0.8.0

Steps to reproduce

No response

Relevant log output

No response

Additional context

No response

What does this PR do?

I am aiming to create a wrapper for some of the logging so that we can have a prefix for each separate extension.

Screenshot/screencast of this PR

Something similar to this

What issues does this PR fix or reference?

#822

How to test this PR?

Check logs originating from extensions folder for the appropriate names

Signed-off-by: Stefan Frunza [email protected]

Signed-off-by: Dylan M. Taylor [email protected]

What does this PR do?

This pull request alters the behavior of the application when running on Linux. When the close button is clicked, the application will close like a normal application would, instead of attempting to run in the background still or minimize to tray.

The rationale for this change is as follows:

• On GNOME systems, such as Fedora Workstation or RHEL, by default there is no system tray.
  • The workaround for this is ugly - both from a UX perspective as well as cosmetically -- having a menu bar and expecting the user to do File > Quit to close out of the application
  • I made another PR, #668 to hide the menu bar, and the client looks MUCH better IMO, but now a user still has to use the menu bar to close the app normally, and they have to hold Alt to get it to appear.
• Linux is a very different beast with podman than Mac or Windows. While it's super inconvenient to have the podman machine VM unexpectedly close on Mac/Windows, this is simply not a problem on Linux. The GUI for podman desktop simply attaches to a socket, so closing the app doesn't necessarily terminate podman containers. Users will expect that the close button will close the application, and not having it do so will be a bad user experience.

What issues does this PR fix or reference?

Issue #663, and this goes with PR #668.

Closes #471

How to test this PR?

Open the application on Linux and then click the X to close it. Validate that it did, in fact, close.

This has been tested by me to work, but it isn't exactly a complicated change.

Bug description

Apologies, I'm not 100% sure if this is me being stupid or an actual bug but I'm really struggling to find any docs on it. Feel free to close it or point me in the right direction if I've missed something obvious!

I've installed and run Podman Desktop 3.4.4, I have both podman and docker engine installed. While podman-desktop is picking up the podman volumes, images, and containers it hasn't picked up anything from docker engine, despite the extension saying it's running.

I'm using docker engine for vscode dev containers since podman doesn't quite seem to work with it yet.

I've taken a look at the dev tools console and the only errors and warnings I can see are the following although since I'm not running lima the error feels unrelated.

I can also see that it is activating the docker extension (it starts and ends just fine by the looks of things).

Operating system

Ubuntu 22.04.01 LTS - Jammy

Version

0.9.1

Steps to reproduce

• Install docker-engine + dependencies as described in docs - https://docs.docker.com/engine/install/ubuntu/.
• Run a container.
• Install podman-desktop 0.9.1.
• Open podman-desktop, and see that no containers, images, or volumes are discovered.

Relevant log output

[warn] main ↪️ APPIMAGE env is not defined, current application is not an AppImage
[...]
[warn] main ↪️ Can not find CRC binary!
[...]
[info] main ↪️ Activating extension (docker)
[info] main ↪️ Activation extension (docker) ended
[...]
[error] main ↪️ Could not find podman socket at /home/user/.lima/podman-lima/sock/podman.sock nor /home/user/.lima/podman-lima/sock/podman.sock

Additional context

Image showing the docker extension installed and running

feat: change background of buttons to circles

What does this PR do?

This PR introduces changing the buttons to have no background, but circles on hover.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

N/A

How to test this PR?

Signed-off-by: Charlie Drage [email protected]

Bug description

Images and containers are not visible on Podman Desktop although they appear with the commands podman image ls and podman container ls -a

Only for images, If I build an image from Podman Desktop, only then the images appear.

Operating system

Windows 10 Pro N (Version 10.0.19041.1806)

Version

0.0.5

Steps to reproduce

1. Opened Podman Desktop
2. Initialized the machine (through the Podman Desktop UI - Home)
3. Ran Podman (through the Podman Desktop UI - Home)
4. Visited the Images tab and no images where available
5. From the powershell the command podman image ls shows me 5 available images
6. From Podman Dekstop I build a new image 7.Now I'm able to see the the images that previously werent visible.

Relevant log output

No response

Additional context

No response

Signed-off-by: Dylan M. Taylor [email protected]

What does this PR do?

Sets the menu bar to auto-hide. It can still be used with alt keys.

Screenshot/screencast of this PR

This is on GNOME 43, showing the patch applied. See #663 for a screenshot of how this looks without the patch.

I tested this on a different machine, running KDE. The only thing I was testing for was that the app still ran and the menu bar was gone.

What issues does this PR fix or reference?

This PR closes #663.

How to test this PR?

Simply open the application.

Bumps @docker/extension-api-client-types from 0.3.2 to 0.3.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Is your enhancement related to a problem? Please describe

For every tab under the Container view (Logs, Inspect, Kube, Terminal, Details), the font is a bit too tiny for my weary eyes 👀

Describe the solution you'd like

Perhaps the base scale could be increased? Could also just be me.

Describe alternatives you've considered

• It does work with dpi scaling but I'd rather not enlarge everything.

• Getting a new pair of glasses.

Additional context

I'm testing on Windows with 1440p.

Bug description

When I install the app, click to open it, it just stays like this, no progress. Here is my device info

Operating system

macOS Montery 12.6.1 (21G217)

Version

0.10.0

Steps to reproduce

Actually, I don't know if anyone else has the same problem as me. But for me it's still the same after uninstalling and reinstalling.

Relevant log output

I click 'Toggle Developer Tools' and what its console print is like the additional context displayed.

Additional context

Bug description

My images are stored on a private GitLab repository, which is using a non-standard port number; as a result, the repository name has a colon (:) in it.

example.cqu.edu.au:1234

However, in the Images tab in Podman Desktop, it appears as though the image/tag names are simply being split on by colon, with the second-from-beginning segment being assumed to be the tag, which is not always true. Because of this, I cannot actually see what my images' tags are.

(The tags for each image above should be main-latest, 8.2-base-latest, and 8.2-builder-latest, respectively.)

If I understand how image tagging works correctly, then it would be better to treat the final segment as the tag, and everything else as the combined repository/image name.

Operating system

Windows 11 22H2

Version

0.10.0

Steps to reproduce

No response

Relevant log output

No response

Additional context

As an aside, I couldn't actually see where my Podman Desktop version was from within the app; had to find the exe on disk and use the file details.

Is your enhancement related to a problem? Please describe

We have no documentation indicating Kind (or any other "hidden" provider such as Lima..) on the site, other than a very small entry on the front page listing container engines.

We need to have a document that lists all the supported container engines as well as the capabilities of each of them (for example, we provide Podman docker socket compatibility support, we provide Kind support, we also provide being able to start/stop Lima VM's).

This can either be a matrix or table listing all the providers.

At the moment it's all "hidden" away and only enables if Podman Desktop detects the binary.

Describe the solution you'd like

More documentation on site on each container engine / more elaborate explanation of what's happening

Describe alternatives you've considered

No response

Additional context

No response

Is your enhancement related to a problem? Please describe

When creating a pod, we should show what is accessible within the pod, environment variables which are shared between pods, networking, etc.

Right now the page is very blank and documentation is lacking on what Pods actually "do".

Describe the solution you'd like

More information with regards to pod creation.

Describe alternatives you've considered

No response

Additional context

No response