Building from source on Windows, and building the container image #678
Replies: 5 comments 1 reply
-
Also, when building the docker image from Windows, I had to change a couple things:
When I changed these things, it worked to run the image in Cloud Run, with something like this:
And then I could set that as a scheduled task, to run every 15-20 minutes or whatever. |
Beta Was this translation helpful? Give feedback.
-
Using my modified console program, and the image built with the modified Dockerfile.console, I can set that image to run as a Cloud Run job, following these instructions: Thank you very much for building this cool tool. |
Beta Was this translation helpful? Give feedback.
-
I'd also love to be able to specify the location of the config file; I'm running on Kubernetes, which makes it hard to inject a single file into an existing directory (from a config map). |
Beta Was this translation helpful? Give feedback.
-
Created #698 to change how config files are mounted to the container. Slotted for v5 as I think this will likely end up being a non-backwards compatible change. |
Beta Was this translation helpful? Give feedback.
-
Bailey, what about the other stuff I mentioned above?
|
Beta Was this translation helpful? Give feedback.
-
Hi
I wanted to try running the container image from Google Cloud Run. I saw your comment somewhere in the documentation about how containers free people from the big cloud infrastructure providers. But I've got a different set of criteria. Anyway I'd like to just run it in "Cloud Run". Specifically I am talking about the headless option.
Theoretically this could be pretty easy, as Cloud Run just runs an image. So I can do this:
(that works in Windows PowerShell, where the backtick is the newline continuation character)
But to do that, I need to mount a configuration file, and an output directory.
Cloud Run allows me to mount one or more read-only or read/write storage buckets (via gcsfuse). So that would get me close. But there are couple problems here:
/app/output
and/app/configuration.local.json
as far as I can tell from reading the documentation. I looked in the code and it does appear that if there is an argument given to the program, it uses THAT as the directory to look in, for configuration . But this isn't documented. and also I couldn't get it to work properly.therefore, a feature request:
allow the image to get its arguments from the environment. So I could specify
P2G_CONFIG=/mnt/configdir
and it would use the configuration file in that directory. Similarly I could specifyP2G_OUTPUT=/mnt/outputdir
andI tried forking and modifying the C# code, and I'm reasonably ok at that. I was able to build it successfully. The next step was to build the Docker image. But I know much less about Docker. There is no documentation describing how to build the image. I tried on windows. I guessed this:
But that failed, because of errors like this:
So I tried
And that seemed to work.
Therefore, a documentation improvement request:
Document how to build an image from the various Dockerfiles.
Beta Was this translation helpful? Give feedback.
All reactions