-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dockerhub build doesn't seem to work #66
Comments
i found the linuxserver/docker-apprise image - thats what i was expecting, a fully functioning image |
I certainly welcome pull requests if you want to try to improve the docker setup. My knowledge is geared to Python mostly. The docker setup you see here today is all credit to the community. I re-ran the instructions on my README page and the website seems to host correctly for me. But regardless, I'm sorry i wasn't able to help you and i'm glad you found an alternative solution! 👍 |
@caronc well I have an install to crib off now, and i like your app, and i do know a little about using github actions and docker buildx to make multiarch images whnever code changes. Might take a while but lemme see what i can do :-) |
So i tried for test, it work, your deployment seems use port
|
@martadinata666 yes ithat was me trying 8080 (i had also tried 8000) based on the log output. I have a fork with an amended container i am trying out.... probably a day away if you would like to try it out.... i have it working, just in middle of switch base image to alpine to make it smaller.... but stuck on alpines supervisord implementation. ... plus using the current dockerfile as baseline whatever i do it ends up in large image, the linuxserver.io version seems to take a quite elegant approach but i havent fully unwound that in my head yet as i wanted to try and stay inline with the broad approach already used here for docker. |
I have an initial dockerfile that refactors to use alpine and to get image size down to ~120MB on disk, 39MB compressed Few things:
@caronc let me know if you want me to keep going or back away slowly, lol :-) this is my working config FWIW
|
so here is the wild part, these symptoms was actually caused by a new hyper-v feature affecting the docker swarm ingress network running on my ubuntu VMS! for some reason this app exhibit not found issues, whereas other apps were just really slow (grafana, portainer, etc). just logging reason for issue for posterity. |
Sorry for the delay in response; so just the port mapping is wrong from your standpoint? Your docker-compose.yaml file pulls from a different source: image: scyto/docker-apprise Is there something done differently that you'd prefer to be fixed that exists in mine instead Chris |
Hi, no need to apologize for when you reply!
I was very confused by the instructions and apprise-cli container on GitHub. It didn’t appear that apprise was installed in it. Though it may have been a false positive caused by network issues I was having. As I see it is added in a requirements text file. Not sure as I have t revisited.
In terms of improvements, I think are valuable.
1. much smaller size of image
2. More architectures
3. Automated build and push to dockerhub
All my image on dockerhub is meant to show is the refactored dockerfile in my fork results in smaller image that works. The point is the dockerfile not the compose or image....
My thinking was if you are happy with approach and are interested in 2 and 3 I would do a PR for the changes. I have little interest in maintaining a forked image.
Only possible blocker I have found is that user 33 in alpine is already in use in alpine so I am unclear on right approach, my fear is adding www-data on another uid would be a breaking change and switching to a diff use name/uid would be a breaking change. This may require me switching to alternate base image.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Chris Caron ***@***.***>
Sent: Sunday, February 20, 2022 9:30:26 AM
To: caronc/apprise-api ***@***.***>
Cc: scyto ***@***.***>; State change ***@***.***>
Subject: Re: [caronc/apprise-api] dockerhub build doesn't seem to work (Issue #66)
Sorry for the delay in response; so just the port mapping is wrong from your standpoint?
Your docker-compose.yaml file pulls from a different source:
image: scyto/docker-apprise
Is there something done differently that you'd prefer to be fixed that exists in mine instead caronc/apprise ?
Chris
—
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcaronc%2Fapprise-api%2Fissues%2F66%23issuecomment-1046285304&data=04%7C01%7C%7Cbb9a9cf3111849f3143608d9f496af3f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637809750288072252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZvPXnHeWT6%2Fl9aXGtVw45MDwDYufsbbrnguxjnhb7qE%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACWXVXCCZJCJIFSU5JT4EO3U4EQLFANCNFSM5OTC6QNQ&data=04%7C01%7C%7Cbb9a9cf3111849f3143608d9f496af3f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637809750288072252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=muM2n005ydmyxWsegkB%2BSZDDmAd7v6Ojv%2Bm0sFaEt2I%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
I'm definitely not keen on breaking changes, but if you think there is a better way going forward for everyone and can still maintain the multi-architecture support, then I'm all on board. I'd welcome your PR! 🙂 |
🪲 Describe the bug
I used the following to pull the image from dockerhub, getting a lot of 404 not found for scripts and logos.
I am little unclear why, my expectation is the container published is self contained.
💡 Screenshots and Logs
💻 Your System Details:
you latest docker container
running on latest docker
🔮 Additional context
100% easy using the stack/compose i provided
I am wondering if looking at the examples this assumes I am running a whole bunch of the web interface from a mount - which seems really odd, i think i am missing something here, this doesn't seem like a self container container?
The text was updated successfully, but these errors were encountered: