BUG: cannot run rstudio server in podman container #2887
Comments
|
we have a similar report here: #2886 it can be caused by the firewall |
|
This looks different - #2886 describes the problem that ports cannot be accessed by another container on the same host. @h-vetinari can you do a |
|
Here's some outputs: Then, following redirects: And finally, by faking an appropriate user-agent: |
|
OK - this does not look like a podman problem. The requests are forwarded to the server/port. Maybe the RStudio server is not configured correctly (it looks like the virtual host "localhost:8082") might be the problem. |
Respectfully, with podman advertising that Happy to help debugging that, but it works out of the box with docker. |
|
Just tried this with podman and on my machine (CentOS 7.6 on Azure) it works without any issues. Started the server with: Then on the host machine - this is what I get: |
|
Probably environment-specific, then. |
|
Hm. Logs might not be the most useful, since you're starting the application manually... Any way to get more debug output out of rstudio-server? |
|
One more bit of information: It might be buildah issue after all?
Which version of podman? I tried again with the latest nightly without a difference. Also, did you try to login with
Shouldn't the container abstract all that away?
Unfortunately I can't invest more time today... Will try to check later. |
|
Alright, image issues would make sense. @TomSweeneyRedHat PTAL |
|
@TomSweeneyRedHat |
|
@mheon why do you think this is an image issue? |
|
@rhatdan Image, built by Docker, run by Podman works. Image, build by Buildah, run by Podman, does not work. Seems like it's the image based on that |
|
Sorry @h-vetinari I've not had time to dive into it, chasing other fires. |
@h-vetinari I used the version that ships with CentOS: 0.12.1.2 |
|
@derkoe Is there any differences you see in the environment set for the container image? |
|
I am asking you to inspect the docker build verus the podman build and see if you see anything obvious. |
|
Agree - if you can pastebin the output of |
OK, no problem. Your last comment started with
Here's the output. To clarify vs. OP: I used for the two images. Then the output of the various inspect commands is as follows. Let me know if there's something more you'd need.
|
|
On top of the actual diff from inspect, I'll note that the Docker-built image is probably Docker formatted, while Buildah made an OCIv1 image (unless explicitly told not to) |
|
@mheon "Labels": null,
"Annotations": {},
- "ManifestType": "application/vnd.docker.distribution.manifest.v2+json",
+ "ManifestType": "application/vnd.oci.image.manifest.v1+json",
"User": "",
"History": [After a little googling, I can't seem to find a way to change the ManifestType used by Do you think that somehow this is a case where there's a delta between what docker can do (or has implemented) vs. the capabilities of the OCI image spec? |
|
In Buildah do --format docker And then see if the container works, although I would doubt this is the issue. |
|
@rhatdan |
|
This is working for me in podman. rpm -q podman podman run --rm -it -p 8082:8787 localhost/podman_testroot@5244c2c286fa:/# rstudio-server start |
|
@rhatdan Also, did you try to log in with the credentials that are set in the dockerfile ( |
|
No I did not try that, Could you attempt to build podman from master and see if it works there on ubuntu. |
|
Login works. |
|
I tried to build podman today, but installing the required dependencies on the machine I have available would uninstall docker-ce, which I can't do because it's in active use for other purposes. I'll have to start a new VM and try some other time. |
|
Yes docker-ce is |
|
@rhatdan @lsm5 @mheon Summing up: following the build instructions (as closely as possible) leads to a podman build that does not have the issue in the OP. Consequently, this issue seems to be a problem with the way the |
I looked at opening an issue at moby, but it seems that while they're waiting for runc 1.0.0, they have decided to solidify the "provides runc", see here See also https://github.com/containerd/containerd/blob/master/RUNC.md... Do you still think it's worth filing an issue to stop providing runc? |
|
Yes please do. |
|
Done. How can we move the needle on this issue with (very likely) the ubuntu packaging? |
Please feel free to chime in in the issue I opened on the moby tracker. |
|
Not sure that will help. :^) |
@rhatdan @lsm5 |
|
After getting to try out the new podman 1.3.2 (following #3044), I can report that the problem has been fixed also in the rhel-packaged world. Thanks everyone here for the help and @fatherlinux for delivering the extras-version-bump early! |
github-actions
bot
added
the
locked - please file new issue/PR
When I first tried podman, the following was the core issue that forced me to abandon podman again (resp. at least try with the most current version; which lead to #2250). All the other little issues (cf. e.g containers/buildah#1456 or the others referenced in #2250) could be worked around with some effort, but I didn't find a solution to the following.
Say we have the following dockerfile, and call it
podman_studio.dockrf:This installs the current preview of RStudio Server into a container, and adds a test user. Building and running this with docker, one can start the server from inside the container:
One may then enter the logins we specified above:
And arrives at the actual R session:
Doing the same with podman (version
1.3.0-devfrom the latest nightly), i.e.it's clear that something is there on
localhost:8082; it forwards to/auth-sign-in, but never actually manages to load the page correctly.The text was updated successfully, but these errors were encountered: