| [17:41:51] | * postmanpat[m] has joined #farmos |
| [17:41:51] | <postmanpat[m]> | I pull the latest 3.x-dev image, but I don't get an update. Everything is still in the same version. |
| [17:41:51] | <postmanpat[m]> | What am I missing? |
| [17:49:35] | <mstenta[m]> | Hi postmanpat - what are you looking at and what are you expecting to see? |
| [17:50:25] | <postmanpat[m]> | I try to do my first update of farmos. Starting with the dev-stack. I'm on 3.2.2 |
| [17:51:21] | <mstenta[m]> | When you say "everything is still in the same version", what are you referring to? |
| [17:51:27] | <mstenta[m]> | Screenshot perhaps? |
| [17:52:01] | <postmanpat[m]> | php, drupal at least. |
| [17:52:43] | <postmanpat[m]> | ACTION uploaded an image: (106KiB) < https://matrix.org/oftc/media/v1/media/download/AYhvw_ly1sjGr5P_568DTW6f... > |
| [17:53:32] | <mstenta[m]> | Gotcha |
| [17:53:34] | <postmanpat[m]> | www:... (full message at <https://matrix.org/oftc/media/v1/media/download/AfLwXIuZwIoENP7OaeF8nsC2...) |
| [17:53:51] | <postmanpat[m]> | ah. sorry wrong.. |
| [17:54:19] | <postmanpat[m]> | www:... (full message at <https://matrix.org/oftc/media/v1/media/download/Ae37sfIHhRJsvqXgecAuLmXj...) |
| [17:55:28] | <mstenta[m]> | Ok, two possibilities (that I can think of)... |
| [17:58:12] | <mstenta[m]> | 1. If you ran `docker pull farmos/farmos:3.x-dev`, you need to `docker compose down` and then `docker compose up` for the new image to be used |
| [18:00:38] | <postmanpat[m]> | mstenta[m]: Ok. I just did stop/start in portainer. |
| [18:05:06] | <mstenta[m]> | (And actually the second possibility I thought of probably doesn't apply, based on your screenshot) |
| [18:19:26] | <mstenta[m]> | Did that help postmanpat? |
| [18:21:32] | <postmanpat[m]> | eh.. well... I don't know. Looks messy. |
| [18:21:32] | <postmanpat[m]> | Tried running 'docker compose down' ok |
| [18:21:32] | <postmanpat[m]> | 'Docker compose up' gives error, and I dont have the dev stack in portainer any more. |
| [18:22:30] | <postmanpat[m]> | ACTION uploaded an image: (74KiB) < https://matrix.org/oftc/media/v1/media/download/AeaEsGvwrjT3hIFpXZ2Ic1HS... > |
| [18:23:27] | <mstenta[m]> | Hmm looks like you still have a PostgreSQL container running? |
| [18:24:37] | <mstenta[m]> | It's basically saying that it can't start your PostgreSQL container because port 5432 is already used by another service |
| [18:24:48] | <mstenta[m]> | (Another PostgreSQL) |
| [18:25:12] | <mstenta[m]> | Oops I mean 5434 |
| [18:25:19] | <postmanpat[m]> | yep. I think I'll get it, just need some time. It's late here.. |
| [18:25:48] | <mstenta[m]> | Same here. About to have dinner so I might disappear :-) |
| [18:26:59] | <postmanpat[m]> | Ok. Thanks. Portainer just rearranged the stacks. It was there at the bottom. |
| [18:26:59] | <postmanpat[m]> | So problem is perhaps how do I run docker-compose down on a stack setup in docker.. |
| [18:27:20] | <mstenta[m]> | Hmm not sure. Never used portainer |
| [18:29:02] | <postmanpat[m]> | I copied the docker-compose.yml to a folder, and ran docker-compose down from there. It worked. |
| [18:29:02] | <postmanpat[m]> | Docker-compose up messed up, and created a new stack with only a db-container |
| [18:43:33] | <postmanpat[m]> | ACTION uploaded an image: (95KiB) < https://matrix.org/oftc/media/v1/media/download/AT806F6sIFAt09IE0fhKWhsO... > |
| [18:44:39] | <postmanpat[m]> | Got it running again. |
| [18:44:39] | <postmanpat[m]> | Removed the containers in the stack and recreated them with an image pull. That din't bring any updates |
| [18:44:39] | <postmanpat[m]> | I'll sleep on it. |