Update Docker image to latest release 1.29.2, add PR with image fixes #70
Comments
|
To help phrase the current evolutionary stage of this effort, I think it would be valuable to re-examine the purpose(s). (I must admit I am not being selfless here - the answers would also help me greatly in terms of contributing time and energy to this effort if I am made much more clear on its aims and intended audience). Here's some framing questions that I would like to use to kick off the process of clearing up the context of this resource: What I'd love to understand better is the following:
Answers will help me a lot because I find the current situation quite confusing. I should also state that my personal experience with the "Backdrop Official Docker Image" was disappointing. I am sure there's a very clear set of reasons that produced the current setup, I just don't know what they are. |
|
I've applied the Pull Request, and updated the readme file changes from @ProfessorGram . After making the updates, I tested the docker image, and was able to start it, but the image was not able to write files so Backdrop never started. It looks like we will need some additional tooling to make this really useful.
|
|
I have made a top-to-bottom update of the README.md file in order to cater
to both Backdrop and Docker newbies.
There may be a requirement to "mount" specific directories in the docker
images to a non-immutable location in the filesystem created by Docker.
The installation I used from orwa worked fine, btw.
Here's the compose.yml from the machine currently running Backdrop in a
Docker container (non-persistent, but able to install and run)
```
services:
backdrop:
image: orwa84/backdrop
ports:
- 8080:80
environment:
BACKDROP_DB_HOST: db
BACKDROP_DB_USER: backdrop
BACKDROP_DB_PASSWORD: backdrop
db:
image: mysql
environment:
MYSQL_USER: backdrop
MYSQL_PASSWORD: backdrop
MYSQL_ALLOW_EMPTY_PASSWORD: 'yes'
MYSQL_DATABASE: backdrop
```
...step-by-step...
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On Fri, Dec 27, 2024 at 8:17 AM Wilbur Ince ***@***.***> wrote:
I've applied the Pull Request, and updated the readme file changes from
@ProfessorGram <https://github.com/ProfessorGram> . After making the
updates, I tested the docker image, and was able to start it, but the image
was not able to write files so Backdrop never started.
It looks like we will need some additional tooling to make this really
useful.
- Do we need to install the bee cli?
- Do we need to make writable folder to hold configuration files?
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASY3R3HOFMUOTSIPT5LKGXT2HSMAVAVCNFSM6AAAAABUHLRZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTGE4DOMRRGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@ProfessorGram I've merged in all our PR's, so please just add you text updates to a new PR and we can merge that. I tested with the orwa84/backdrop image, and that is working but uses the 1.29.0 image. I guess we need to push our image before we will get the latest version. Can you test all the code links in the README file? I changed the contents of the console code blocks. |
|
Hello there!
How about we get *any* version up and running on Docker, then tweak the
README.md to suit?
What do you think? I'm happy to fine-tune the README.md against any
working version.
If you're free, let's hop on a quick zoom?
https://us06web.zoom.us/j/81528308889?pwd=G3aJBc4b6gMyb8R0DOOROYb8cpOsDb.1
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On Fri, Dec 27, 2024 at 11:12 AM Wilbur Ince ***@***.***> wrote:
@ProfessorGram <https://github.com/ProfessorGram> I've merged in all our
PR's, so please just add you text updates to a new PR and we can merge that.
I tested with the orwa84/backdrop image, and that is working but uses the
1.29.0 image. I guess we need to push our image before we will get the
latest version.
Can you test all the code links in the README file? I changed the contents
of the console code blocks.
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASY3R3FHO27RB7F3WRWF2JT2HTAQLAVCNFSM6AAAAABUHLRZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTGI3DQOBUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@ProfessorGram I assigned this to you, all we need is the updated readme file. Go ahead and create a pull request, and we can get that worked out! |
|
OK, will do.
Thanks for everything!
…On Sat, Dec 28, 2024 at 12:15 AM Wilbur Ince ***@***.***> wrote:
@ProfessorGram <https://github.com/ProfessorGram> I assigned this to you,
all we need is the updated readme file. Go ahead and create a pull request,
and we can get that worked out!
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASY3R3AQDZB4DQ3AEYEHYZD2HV4K7AVCNFSM6AAAAABUHLRZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTHA2DCNZTGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I have updated our existing readme file, and created a pull request at docker hub official images. Once this is pushed, we can fully test or image updates and confirm it is working as intended. When that is complete, we will update the readme file with exact usage instructions. Stay tuned! |
|
I've also updated the documentation for updating the docker images. |
|
There's an issue with an 'expose' command in the dockerfiles for apache and fpm. I have updated that, and fixed the gitcommit hash, and resubmitted the merge request. |
|
@diraneyya we are trying to get your work on #69 published, but the reviewers have questions about some change to the apache dockerfile that was not made on the fpm dockerfile. They questioned the inclusion of 'EXPOSE 80'. Can you take a look at that conversation and weight in? I am just managing the updates, but am not able to test them to tell if they are working. We are going to do testing and updating once the image is published. Thanks in advance! |
|
@Wylbur Sure I just replied. |
|
@diraneyya Thanks so much! The image was out of date because I stopped updating it. There were issues I could not solve, and did not have resources to help me figure it out. Your PR changed all that. Going forward we will keep it up to date. Graham and I are committed to maintaining this, and are working to really understand how it works. I appreciate your question about how the process works that you posted in the other issue. I think they have an automated system for generating images, and the creators of the backdrop images set us up to use their system. It will be good for us to have a good understanding to keep this running. |
|
Hello Wilbur and Orwa,
Yes, let's get a stable production 1.29.x version up and running and get
the production process nailed down so the upcoming 1.30.0 release of
Backdrop (~Jan 15) is silky smooth.
Many thanks to you both for getting elbows deep.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On Sat, Jan 4, 2025 at 11:26 AM Wilbur Ince ***@***.***> wrote:
@diraneyya <https://github.com/diraneyya> Thanks so much!
The image was out of date because I stopped updating it. There were issues
I could not solve, and did not have resources to help me figure it out.
Your PR changed all that. Going forward we will keep it up to date.
Graham and I are committed to maintaining this, and are working to really
understand how it works. I appreciate your question about how the process
works that you posted in the other issue. I think they have an automated
system for generating images, and the creators of the backdrop images set
us up to use their system. It will be good for us to have a good
understanding to keep this running.
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASY3R3FFKYX4OQHRVA6NGV32I5IEVAVCNFSM6AAAAABUHLRZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZQGAZDSOBWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
It would be my pleasure to answer any questions you may have on Docker and to get you unstuck. When I started working with Docker 5 years ago, I remember that it was a steep learning curve for me and I always had questions, but not many people around me were as good teachers as they were coders. So I am here to support you, you just have to ask. I can also meet in video if this helps.
What is required from this point on, with regard to the official images? There are still no recent tags on Docker Hub. Regards, |
|
The pull request on the other issue needs to be resolved, then the new image will be built. So we're just waiting for them to approve and push the changes. |
The repo has not been update regularly, and there are some issues with the image itself. We will use this ticket to assemble documentation about making updates, and create some kind of process to test the image and confirm it is working.
We already have a pull request to work with, and will try to use that: #69 .
Here is the location of the current documentation for the process:
https://github.com/backdrop/backdrop-issues/wiki/Update:-Docker-Image
The text was updated successfully, but these errors were encountered: