IRC logs for #farmOS, 2024-01-15 (GMT)

2024-01-14
2024-01-16
TimeNickMessage
[04:47:55]<tamtran94[m]>ACTION uploaded an image: (98KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/piwivkcKqQSqdRhi... >
[04:54:40]<tamtran94[m]>Excuse me, may I continue the discussion on the topic at [https://farmos.discourse.group/t/database-error-installing-farmos/1503/7]()... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/LmIHVSsSEsNPxbLC...)
[06:11:19]<mstenta[m]>tamtran94: What Docker image are you using? symbioquine's example that you replied to in that forum topic used `farmos/farmos:2.x-dev`, but if you are running farmOS 3.0.0 then you should use `farmos/farmos:3.x-dev`
[06:11:37]<mstenta[m]>(And actually if you aren't doing development it's better to run farmos/farmos:3.x (no -dev))
[06:11:58]<mstenta[m]>The farmos/farmos:2.x-dev image runs PHP 8.1, whereas farmos/farmos:3.x-dev runs PHP 82.
[06:12:10]<mstenta[m]>8.2*
[07:28:26]<mstenta[m]>I opened two farmOS.org pull requests - please review!
[07:28:28]<mstenta[m]>https://github.com/farmOS/farmOS.org/pull/87
[07:28:35]<mstenta[m]>https://github.com/farmOS/farmOS.org/pull/88
[07:35:52]<tamtran94[m]><mstenta[m]> "tamtran94: What Docker image are..." <- ```... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/RsvnWkZOOzeaLdyd...)
[07:36:24]<mstenta[m]>Oh OK, and you are still seeing PHP 8.1 in the farmos/farmos:3.x image?
[07:38:16]* farmBOT has joined #farmos
[07:39:25]<mstenta[m]>I'm also curious what is explicitly depending on PHP 8.2... 🤔 but probably easiest to just get onto PHP 8.2...
[07:39:42]<mstenta[m]>Try running docker pull farmos/farmos:3.x to make sure you have the most recent image
[07:39:55]<mstenta[m]>It's possible that an older 3.x image was PHP 8.1
[07:40:11]<tamtran94[m]>ACTION uploaded an image: (172KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/aDZVWBoCQSONQmBn... >
[07:40:12]<mstenta[m]>The farmOS images inherit from the official Drupal images, so we just get whatever they have
[07:41:46]<mstenta[m]>Note that you need to destroy and recreate your farmOS container after you run docker pull, otherwise it won't use the new one
[07:42:01]<mstenta[m]>(docker compose down will destroy the container)
[07:43:32]<tamtran94[m]>mstenta[m]: Dear, I can't see components PHP 8.1 while installed. But If the host showed message like that, figure it out PHP version 8.1
[07:43:32]<tamtran94[m]>and if we can't upgrade as follow notified above. So, 12 hours next (GMT +7), I'll visit company's office and try again with it.
[07:43:32]<tamtran94[m]>Mr. mstenta
[07:45:50]<mstenta[m]>Maybe you already know this, but just to be clear: the PHP version inside the Docker image and the PHP version on the host computer that is running Docker may be different. The host PHP doesn't matter at all if you are using Docker. The Docker container is what's serving farmOS.
[07:46:23]<mstenta[m]>The Docker image is completely self-contained with all the requirements to run farmOS, including Apache, PHP, Composer, etc
[07:46:32]<mstenta[m]>So all the host needs is Docker
[07:46:52]<mstenta[m]>(just want to make sure that's understood)
[07:51:33]<tamtran94[m]>Yes, I used Docker.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/vpShqIIDDhUlgdTI...)
[07:52:46]<mstenta[m]>If Apache is already installed on the host, you may have issues with port conflicts because both Apache and Docker will want to use ports 80/443. You should probably uninstall Apache from the host to make things easier for you.
[07:54:24]<mstenta[m]>I don't know if that's causing you issues or not... just suggesting it to keep things simple. The host just needs Docker, not Apache or MariaDB/MySQL/PostgreSQL - those can all be in Docker containers
[07:54:45]<mstenta[m]>Are you using a docker-compose.yml and running docker compose up/down commands?
[07:55:22]<mstenta[m]>If so, then you don't need to run any docker rm 'container id' ... commands...
[07:56:12]<mstenta[m]>docker compose down will destroy (rm) containers. It will not rm images though. But if you run docker pull farmos/farmos:3.x then that will replace the image you have with the latest one
[07:56:22]<mstenta[m]>So that when you run docker compose up again, your container will use that image
[07:56:39]<tamtran94[m]>mstenta[m]: Yes, Mr. mstenta
[07:56:39]<tamtran94[m]>I edited docker-compose.yml as mr. symbioquine suggest on previous topic
[07:56:50]<mstenta[m]>(Assuming you ran docker compose down to destroy the containers first... if not, then docker compose up will just start the container using the old image)
[07:58:25]<tamtran94[m]>tamtran94[m]: > <@tamtran94:matrix.org> Yes, Mr. mstenta... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/yqNLTeOACavTqRhS...)
[07:58:59]<tamtran94[m]>docker rm 'container id' ...
[07:58:59]<tamtran94[m]>docker rmi 'image id' ...
[07:59:55]<tamtran94[m]>Actually, I prefer to use both of command as above, with limited ability for skillful with docker command 😅
[08:02:04]<mstenta[m]>If you are using docker compose then you don't need to run either of those commands. docker compose down will run docker rm 'container id' ... for you
[08:02:29]<mstenta[m]>and docker pull farmos/farmos:3.x will replace the image you have currently with the newer one
[08:02:39]<mstenta[m]>so there's no need to run docker rmi 'image id' ...
[08:51:50]<tamtran94[m]>Thanks Mr. mstenta Have a good day!
[09:12:34]<mstenta[m]>> https://github.com/farmOS/farmOS.org/pull/88
[09:12:35]<mstenta[m]>thanks for the review wotnak !
[09:51:51]<mstenta[m]>I drafted a blog post for farmOS 3.0.0 - if anyone has a sec to review :-)
[09:51:53]<mstenta[m]>https://github.com/farmOS/farmOS-community-blog/pull/24
[09:53:10]<mstenta[m]>Here is the preview: https://deploy-preview-24--farmos-community-blog-preview.netlify.app/blo...
[17:19:45]<mstenta[m]>Thanks for the reviews today wotnak and paul121! I merged all the PRs 🙌