On 1/24/19 5:49 PM, arnaud gaboury wrote:
I am following this wiki[0] to run R Studio on my box. Below are the commands I run

----------------------
# podman run -d -p 8787:8787 -e PASSWORD=XXX --name rstudio rocker/tidyverse
..........
Storing signatures
a72fac512b891c21f0654334a2032b0d67b87720cb986a092237ab272d245f8d
-----------------------------------
At this point, I am supposed to access the R studio app via my Firefox browser on port 8787 on localhost, which I can't.

Debuging:
--------------------------------------------
- Is the container running?
 # podman ls
CONTAINER ID  IMAGE                              COMMAND  CREATED        STATUS            PORTS                   NAMES
a72fac512b89  docker.io/rocker/tidyverse:latest  /init    2 minutes ago  Up 2 minutes ago  0.0.0.0:8787->8787/tcp  rstudio

-Is the 8787 port open?
 # podman port a72fac512b89
8787/tcp -> 0.0.0.0:8787
 # lsof -i -P -n | grep LISTEN
8:cupsd       984   root    8u  IPv6  35102      0t0  TCP [::1]:631 (LISTEN)
9:cupsd       984   root    9u  IPv4  35103      0t0  TCP 127.0.0.1:631 (LISTEN)
67:conmon    12891   root    5u  IPv4 453576      0t0  TCP *:8787 (LISTEN)

- Can I ping localhost, 0.0.0.0, 127.0.0.1, yogabx (hostname), 192.168.1.92 (returned by ip -a)
YES

- Do I have any firewall/iptable running?
 # systemctl status firewalld.service
● firewalld.service
   Loaded: masked (Reason: Unit firewalld.service is masked.)
   Active: inactive (dead)
NO iptables

# curl localhost:8787
curl: (7) Failed to connect to localhost port 8787: Connection refused

# podman logs a72fac512b89
[fix-attrs.d] applying owners & permissions fixes...
[fix-attrs.d] 00-runscripts: applying...
[fix-attrs.d] 00-runscripts: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] add: executing...
Nothing additional to add
[cont-init.d] add: exited 0.
[cont-init.d] userconf: executing...
[cont-init.d] userconf: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise rstudio: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise rstudio: warning: unable to spawn ./run - waiting 10 seconds
..... and so on

----------------------------

Googling this issue (s6-supervise (child): fatal: unable to exec run: Permission denied), I found a few reported issues like this one[1],[2]
I don't understand what is behind, so can anyone help me to solve this issue (if I can).

Thank you





_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Permission denied often indicates and SELinux issue?