Issue Description
Recently had a crash, and re-installed with the newer versions (which I could remember what version I had backend prior) The reason I say similar to #24025 is I looked it over, and the config file looks similar, and I believe something to do with the issue. Network showing Aard(sp) as wll as Pasta, but nothing listed on Pasta in config. Ports added to a container all show --> 0.0.0.0 port. I have loaded several scripts all to no avail. It doesn't matter what port or what IP I set, I'm not able to see anything outside the container.. I had no probems with this on the older version, and actually believe it had a kind of nice feature where if the port on the Windows side was in use it would simply route the internal port to an available port. I noticed it now checks if the port is available and will not create a container if so.
I'm using the latest downloads, and Ubuntu:latest I've tried using localhost:port 0.0.0.0:port localIp:port and even the 127.0.0.1:port the last I know is locked.. I've also made sure firewall/etc was all completly disabled to overrule that being an issue.
Also strange, AI was trying to help me figure this out, and had me run nginx as a quick test after a few adjustments to settings, This worked and I could see the Welcome page that it defaults to. So thought we had it fixed, loaded a fresh Ubuntu:latest set a few ports installed the script, again nothing. Also not sure if they are supposed to change, but it would be nice if the ports would show the address they are linked to once linked to be able to easily see things are working.. I've tried numerous things and nothing has worked, including trying to switch over to Pasta completely, but that seems to fail as well even when changed via ssh in the main database. As I thought Rootless was supposed to use Pasta..
Steps to reproduce the issue
Steps to reproduce the issue
- Install newest Windows Podman & Desktop versions from websites
- WSL2 Rootless setup
- Pull Ubuntu:latest and basic setup add whatever ports (above 1024) 5412, 8080, 8001, 11434
- Install any program that displays itself on a web 'server' output and insure that it isn't using 127.0.0.1
Describe the results you received
Load Chrome point to above address:port -- No response. No matter what IP:Port I get no response. Have even tried ipconfig and used the container local IP - which I noticed container lists and matches computer, but it does not show a default Gateway. - however everyhing in the container works fine, ie: git clone and installation of other tools via http methods
As mentioned, trying nginx as a quick test to see if things were working, had no problem loading its welcome script. The scripts I'm loading were previously running without problems on this computer with an older version of Docker CLI, but started having errors thrown for other reasons and I figured I would just start over. Numerous installs of front and back same results.. - Also have made sure to wipe all traces for Clean Install
Describe the results you expected
Launched web app to load.
podman info output
I allready uninstalled again in frustration.. But files were downloaded from Podman Desktop website Newest Windows version - which installs the backend version during script (thats how I know its a clean version, otherwise it loads Podman Desktop and then notices the backend isn't running) WSL2 when asked and stay Rootless.
Once system is running Pull new Ubuntu:Latest add a Port or 2 depending on script. Load container, basic Ubuntu setup - apt update && apt upgrade -y install git, nano, python3, python3-pip GIT known working script install requirements and run.
Podman frontend Backend and Compose - other features available not installed.
System is Windows 11 Pro Insiders Beta Ryzen 7 7700X 64gb Ram AMD 9060
Other software working, Llama, LMStudio, AnythingLLC, Jan, Cursor, VS Code, WSL2 (tested for newest version)
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
I will probably try again, especially if I see any good response here. I was trying to make due with windows .Venv built-ins today, but a lot easier for coding with AI to have something we can both SEE. and don't have to turn on/off. Not a fan of Docker, Podman has always got the job done, and much 'lighter' to run, coming from not running containers before, they have both been a challenge, but I've become acquinted with Podman, especially now with the Pull containers, and learning Compose commands. - Only complaint prior was having to load ports on a container before creating, so I just learned to add 4 or 5 on each and they would forward and function for whatever I needed to do.
Additional information
Only thing I haven't tried is Non-Rootless, but thats the other half of the reason I run Podman over Docker, less overhead, always worked on older version. 3 or 4 installs now, including setup of backend prior to front, all same results.
Issue Description
Recently had a crash, and re-installed with the newer versions (which I could remember what version I had backend prior) The reason I say similar to #24025 is I looked it over, and the config file looks similar, and I believe something to do with the issue. Network showing Aard(sp) as wll as Pasta, but nothing listed on Pasta in config. Ports added to a container all show --> 0.0.0.0 port. I have loaded several scripts all to no avail. It doesn't matter what port or what IP I set, I'm not able to see anything outside the container.. I had no probems with this on the older version, and actually believe it had a kind of nice feature where if the port on the Windows side was in use it would simply route the internal port to an available port. I noticed it now checks if the port is available and will not create a container if so.
I'm using the latest downloads, and Ubuntu:latest I've tried using localhost:port 0.0.0.0:port localIp:port and even the 127.0.0.1:port the last I know is locked.. I've also made sure firewall/etc was all completly disabled to overrule that being an issue.
Also strange, AI was trying to help me figure this out, and had me run nginx as a quick test after a few adjustments to settings, This worked and I could see the Welcome page that it defaults to. So thought we had it fixed, loaded a fresh Ubuntu:latest set a few ports installed the script, again nothing. Also not sure if they are supposed to change, but it would be nice if the ports would show the address they are linked to once linked to be able to easily see things are working.. I've tried numerous things and nothing has worked, including trying to switch over to Pasta completely, but that seems to fail as well even when changed via ssh in the main database. As I thought Rootless was supposed to use Pasta..
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Load Chrome point to above address:port -- No response. No matter what IP:Port I get no response. Have even tried ipconfig and used the container local IP - which I noticed container lists and matches computer, but it does not show a default Gateway. - however everyhing in the container works fine, ie: git clone and installation of other tools via http methods
As mentioned, trying nginx as a quick test to see if things were working, had no problem loading its welcome script. The scripts I'm loading were previously running without problems on this computer with an older version of Docker CLI, but started having errors thrown for other reasons and I figured I would just start over. Numerous installs of front and back same results.. - Also have made sure to wipe all traces for Clean Install
Describe the results you expected
Launched web app to load.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
I will probably try again, especially if I see any good response here. I was trying to make due with windows .Venv built-ins today, but a lot easier for coding with AI to have something we can both SEE. and don't have to turn on/off. Not a fan of Docker, Podman has always got the job done, and much 'lighter' to run, coming from not running containers before, they have both been a challenge, but I've become acquinted with Podman, especially now with the Pull containers, and learning Compose commands. - Only complaint prior was having to load ports on a container before creating, so I just learned to add 4 or 5 on each and they would forward and function for whatever I needed to do.
Additional information
Only thing I haven't tried is Non-Rootless, but thats the other half of the reason I run Podman over Docker, less overhead, always worked on older version. 3 or 4 installs now, including setup of backend prior to front, all same results.