Re: trying to run the Roundup docker image

Great, this helps a lot! I was able to run the demo tracker by changing the
line to run the following:
docker run --rm -p 127.0.0.1:8917:8080 --name roundup_demo -v
C://users/tmikk/Documents/roundup-demo/usr/src/app/tracker
rounduptracker/roundup:latest demo

I am not sure though how to run the image on Windows so that I could
configure my own tracker. But I think I will leave it at that for now. I
probably won't be using a Docker container to run Roundup.

I also looked into installing Docker on RedHat 7, but wasn't successful.
Followed a couple of guides, but didn't get it to work. I will try using
the Postgresql backend on RedHat 7 if I can get the libraries to work.

On Tue, Nov 14, 2023 at 2:18 PM John P. Rouillard <[email protected]> wrote:

> Hi Tonu:
>
> In message
> <CABDFm8jjuXKmbyobTOQZK8yi_5MDgkNuJ3kLzK3BHse9QGU-AA@mail.gmail.com>,
> Tonu Mikk via Roundup-users writes:
> >I attempted to run the Roundup docker image
> ><https://hub.docker.com/r/rounduptracker/roundup> and wasn't able to
> figure
> >it out.
>
> The installation guide has a section on running demo mode:
>
>
> https://roundup-tracker.org/docs/installation.html#demo-mode-using-docker
>
> however it expects to run with a Linux/Unix docker environment.
>
> I have never used docker in Windows. If your RedHat 7 box can run
> docker you may have more luck. But the version of Docker available
> there may be old enough that you will run into other issues.
>
> >I have the Docker desktop installed on my Windows 10 computer. I
> >then searched and found the Roundup docker image in the Docker Hub. I
> >pulled it. When I run the image in the Docker Desktop I get the following
> >printed out in the logs shown in Docker Desktop.  I have a feeling I am
> >doing something wrong, just not sure what.
> >
> >2023-11-14 10:00:26 Traceback (most recent call last):
> >[...]
> >2023-11-14 10:00:26     template = self._get_choice(
> >2023-11-14 10:00:26                ^^^^^^^^^^^^^^^^^
> >2023-11-14 10:00:26   File
> >"/usr/local/lib/python3.11/site-packages/roundup/admin.py", line 409, in
> >_get_choice
> >2023-11-14 10:00:26     argument = self.my_input('%s [%s]: ' % (prompt,
> >default))
> >2023-11-14 10:00:26
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >2023-11-14 10:00:26 EOFError: EOF when reading a line
> >2023-11-14 10:00:26 Installing issues tracker in tracker
> >2023-11-14 10:00:26 Templates:: jinja2, minimal, responsive, devel,
> classic
> >2023-11-14 10:00:26 Select template [classic]:
>
> It looks like you started the container in config mode but without
> interactive and terminal mode. You must use the -it flags as shown in:
>
>
> https://roundup-tracker.org/docs/installation.html#configuring-roundup-in-the-container
>
> >When I attempt to run the "instant gratification" of the demo tracker. I
> >first opened a command prompt and then did the tried to run
> >
> >> docker run --rm -p 127.0.0.1:8917:8080 --name roundup_demo -v \
> >>    $PWD:/usr/src/app/tracker rounduptracker/roundup:latest demo
>
> The command line expects a Unix shell (e.g. bash), but you are using
> windows cmd shell. So the \ at the end of the line doesn't join the
> two lines above. As a result docker doesn't see any of the arguments
> on the second line and reports the error above.
>
> You should be able to get past this by pasting the first and second
> lines (before and after the '\'; note don't paste the '\') on the same
> window command line.
>
> >and got this:
> >
> >--C:\Users\tmikk\Documents\roundup-demo>docker run --rm -p 127.0.0.1:8917
> :8080
> >--name roundup_demo -v \
> >"docker run" requires at least 1 argument.
> >See 'docker run --help'.
> >
> >Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
> >
> >Create and run a new container from an image
> >
> >C:\Users\tmikk\Documents\roundup-demo>   $PWD:/usr/src/app/tracker
> >rounduptracker/roundup:latest demo
> >'$PWD:' is not recognized as an internal or external command,
> >operable program or batch file.
>
> Yup. The Windows command shell split that into two two separate
> lines/commands (docker and the line starting with $PWD). Docker needs
> to see one long command line.
>
> Also $PWD is replaced by the Unix shell with the current working
> directory (PWD => print working directory). I think the equivalent
> under windows is %CD%, but you may need to type the actual working
> directory.  The working directory will be the parent directory of your
> tracker's home directory.
>
> As I said I don't use docker under windows, so YMMV. Maybe somebody
> else on list is more familiar with the windows docker environment.
>
> Also you probably want to read:
>
>
> https://roundup-tracker.org/docs/installation.html#running-in-demo-mode-with-docker
>
>
> https://roundup-tracker.org/docs/installation.html#configuring-roundup-in-the-container
>
>
> https://roundup-tracker.org/docs/installation.html#running-your-container
>
> Also one open issue with the docker install is receiving
> email. Sending email works with the use of an external email server.
> Receiving email probably requires setting up something using the
> host's crontab (or Task Scheduler on Windows) with a command like:
>
>    docker exec roundup-tracker roundup-mailgw tracker \
>          imap username:password@imap_server inbox
>
> (again join the two lines omitting the '\' if you use the Task
> Scheduler). This might be a solution if you can use pop/imap to
> receive email. If you are not receiving/interacting with issues via
> email you don't have to worry about roundup-mailgw.
>
> Have a great day.
>
> --
>                                 -- rouilj
> John Rouillard
> ===========================================================================
> My employers don't acknowledge my existence much less my opinions.
>


-- 
Tonu Mikk
Developer | Disability Resource Center | disability.umn.edu
University of Minnesota | umn.edu
[email protected]
Pronouns: He/Him

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users