coop-cloud/lasuite-docs
2
0
Fork 1
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Specify user for containers and upgrade to v4.0.0 #10

Merged
notplants merged 6 commits from specify-user into main 2025-12-03 20:15:31 +00:00
Conversation 3 Commits 6 Files Changed 2 +12 -8
notplants commented 2025-12-03 02:14:28 +00:00
Owner
Copy Link

While working on deploying this recipe to the autonomic test instance, I started seeing this error when attempting to connect to containers via bash, or when running the healthcheck (which caused deployment to fail):
invalid USER value 1001:127:-1000

I looked into it, and this strange string was the default docker user set for these containers. I was able to avoid the error by connecting to the containers via docker exec --user root -it containerid /bin/sh. Then I went and added a specific user to the docker compose specs for the container, basically copying from https://github.com/laurentS/lasuite-docs/blob/main/docker-compose.yml

This fixed the issue, and is included in this PR. Although I never figured out why the error randomly started appearing all of a sudden. I have no explanation (maybe a docker upgrade? although I only saw it on the test instance and not the original deployment).

Anyway, it is working now (🌿) so leaving the mystery for now...

I also updated the images to their latest version, 4.0.0, while trying to debug this... to see if that would fix the issue on its own (it did not), but good to upgrade anyway.

While working on deploying this recipe to the autonomic test instance, I started seeing this error when attempting to connect to containers via bash, or when running the healthcheck (which caused deployment to fail): ```invalid USER value 1001:127:-1000``` I looked into it, and this strange string was the default docker user set for these containers. I was able to avoid the error by connecting to the containers via `docker exec --user root -it containerid /bin/sh`. Then I went and added a specific user to the docker compose specs for the container, basically copying from https://github.com/laurentS/lasuite-docs/blob/main/docker-compose.yml This fixed the issue, and is included in this PR. Although I never figured out why the error randomly started appearing all of a sudden. I have no explanation (maybe a docker upgrade? although I only saw it on the test instance and not the original deployment). Anyway, it is working now (🌿) so leaving the mystery for now... I also updated the images to their latest version, 4.0.0, while trying to debug this... to see if that would fix the issue on its own (it did not), but good to upgrade anyway.
notplants added 5 commits 2025-12-03 02:14:28 +00:00
debugging f49e0f5158
debugging bd3c2c17d2
Working by adding user:1000 to recipe 41c73faa24
remove unnecessary 163eea1ba7
update version number 1962ab7c8f
notplants commented 2025-12-03 02:14:42 +00:00
Author
Owner
Copy Link

this pr also updates the image versions to 4.0.0

this pr also updates the image versions to 4.0.0
notplants reviewed 2025-12-03 02:15:36 +00:00
compose.yml
@ -92,2 +92,3 @@
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
- "coop-cloud.${STACK_NAME}.version=0.2.1+v3.4.2"
- "coop-cloud.${STACK_NAME}.version=0.2.2+v4.0.0"
user: "${DOCKER_USER:-1000}"
notplants commented 2025-12-03 02:15:36 +00:00
Author
Owner
Copy Link

not entirely sure why I all of a sudden needed to add these to get this to work... which I don't love

not entirely sure why I all of a sudden needed to add these to get this to work... which I don't love
notplants changed title from Specify user for containers to Specify user for containers and upgrade to v4.0.0 2025-12-03 19:40:54 +00:00
notplants added 1 commit 2025-12-03 20:12:17 +00:00
update label 80adfcafdc
notplants commented 2025-12-03 20:15:20 +00:00
Author
Owner
Copy Link

tested & working. merging

tested & working. merging
notplants merged commit f87c73b953 into main 2025-12-03 20:15:31 +00:00
notplants deleted branch specify-user 2025-12-03 20:15:31 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se fauno flancian Frando iexos jade javielico jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/lasuite-docs#10
No description provided.
Delete Branch "specify-user"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?