Docker image build issues #6
Comments
|
Try to uncomment this line in the Dockerfile and see if this helps |
|
Looks like that fixed it, Are there any plans to publish the image to run this container with docker compose? |
|
@pandaboy6621 I wrote a docker-compose.yml for that'll handle local build. Might be of use version: '3.8'
services:
trmnl:
build:
context: .
dockerfile: Dockerfile
container_name: trmnl
ports:
- "4567:4567"
env_file:
- .env |
|
Thanks, I'll have to check it out
…On Sun, Feb 9, 2025 at 9:00 PM Adrian Lehmann ***@***.***> wrote:
@pandaboy6621 <https://github.com/pandaboy6621> I wrote a
docker-compose.yml for that'll handle local build. Might be of use
version: '3.8'
services:
trmnl:
build:
context: .
dockerfile: Dockerfile
container_name: trmnl
ports:
- "4567:4567"
env_file:
- .env
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP3U57NHI6EYSQ53ZCB2JL32PAW5ZAVCNFSM6AAAAABWI3QSKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWHEZDGMZQGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hey Aidan. 👋 Could you trying using the new |
|
I will try it now and report back |
Looks like the script sucessfully built the image. How can i specify that built image via a docker compose yaml file? |
|
I tried using this version: "3.8"
services:
trmnl:
image: byos_sinatra
container_name: trmnl
ports:
- "4567:4567"
env_file:
- .env
networks: {}And it gave me an trmnl exited with code 0 error Here is the output of the build script And here are my images |
|
Are there any needed values that I have to input into the env? Also I currently don't have the sqlite option added as mentioned here. i can't even find it as a comment to begin with.
|
|
The container this builds is a little unusual, in that it doesn't have a default entrypoint that runs the server or something continuously - the default entrypoint just runs whatever you pass in as a command argument (ref the bin/docker/console script to see it running bash in interactive mode). This works fine if you understand what is going on and how to work with it, but it is a departure from the more common behavior in docker containers for services like this. I think the assumption is that the container's entrypoint will run the service (mine certainly was at first). @pandaboy6621 If you want to "hold" the container open, so to speak, you need to give it something to do forever. You can add |
ℹ️ This'll soon be resolved in this code review when it lands. |
I am trying to build the docker image and get this error. How do i fix this? Are there any plans to make a prebuilt image so this can be run easily in docker compose without us needing ti build the image?
The text was updated successfully, but these errors were encountered: