Giter VIP home page Giter VIP logo

Comments (3)

fresh2dev avatar fresh2dev commented on June 18, 2024

@mkrasmus, thanks for the feedback. In your case it appears that, for whatever reason, the Docker image for rstudio/shiny failed to build.

See this excerpt from the error message you posted:

"message":"No such image: shinystudio_rshiny_rstudio:latest"

What OS are you trying to build this on? Also, please run docker images and reply back with the output of that command. You should see the three "shinystudio_*" images:

REPOSITORY                   TAG
shinystudio_shinyproxy       latest
shinystudio_influxdb         latest
shinystudio_rshiny_rstudio   latest

I'll be happy to work to a solution with you.

from shinystudio.

mkrasmus avatar mkrasmus commented on June 18, 2024

Hi

I am running this on a MacOS Mojave (10.14.4)
Docker Engine (Engine: 18.09.2) & Docker desktop (Version 2.0.0.3 (31259))

Yes I get the images as indicated:

REPOSITORY                                                         TAG                 IMAGE ID            CREATED             SIZE
shinystudio-master_shinyproxy                                      latest              c8e5dcaa3776        17 hours ago        504MB
shinystudio-master_influxdb                                        latest              d450610eadb3        17 hours ago        239MB
shinystudio-master_rshiny_rstudio                                  latest              5fb8a7197085        17 hours ago        3.23GB

When I enter command docker container ls I get this:

CONTAINER ID        IMAGE                           COMMAND                  CREATED             STATUS              PORTS                    NAMES
b1f261ca2b65        shinystudio-master_shinyproxy   "/opt/shinyproxy/sta…"   9 seconds ago       Up 7 seconds        0.0.0.0:8080->8080/tcp   shinystudio-master_shinyproxy_run_1cb93c23f64d
4919ffd75fd5        shinystudio-master_influxdb     "/entrypoint.sh infl…"   9 seconds ago       Up 8 seconds        0.0.0.0:8886->8086/tcp   shinystudio-master_influxdb_1

So the shinystudio-master_rshiny_rstudio doesn't appear. Not sure if that's an issue, but the error suggests it could be.

I've run docker stop <image name> and then docker rm <image name> before rerunning the command ./control.sh setup to build the images but no luck. It does build off a bunch of cached files, so I thought I should remove the cached files as much as possible with docker builder prune -af based on some stackoverflow solutions to that type of issue, but it continues to build from cached files so not sure to address that either. As you can well guess my experience with Docker is at the basic concept level only.

Any suggestions on what I can do next would be welcomed.

Cheers
Michael

UPDATE: Got it working. I should just follow instructions to the letter :)
So after cleaning everything out (docker images and containers) I went through the readme.md one more time and decided to run the git clone https://github.com/dm3ll3n/ShinyStudio command instead of just saving the zip file, unzipping and then running the ./control.sh setup from inside the ShinyStudio folder. Not sure why that was an issue in the first place, I thought cloning and downloading and unzipping would lead to the same deal but anyway. Mark issue as closed, thank you.

from shinystudio.

fresh2dev avatar fresh2dev commented on June 18, 2024

Fantastic, glad you got it working. When you download a zip of the repo, GitHub appends the branch name “-master” to the name of the directory. In turn, your Docker images were named with “-master” in the name, so ShinyProxy was unable to find an image with the exact name shinystudio_rshiny_rstudio. When you git clone a repo, the downloaded folder does not get “-master” appended to it, so the images will be named as expected. I’ll explore ways to ensure the project name is consistent regardless of name of the directory.

EDIT: to add to this... You won’t see any shinystudio_rshiny_rstudio containers running until you open a panel within ShinyProxy. Notice that, when you sign out of ShinyProxy (or are idle for a while), those containers will be destroyed.

from shinystudio.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.