Specify user for containers and upgrade to v4.0.0 #10
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/lasuite-docs#10
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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:-1000I 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.ymlThis 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.
this pr also updates the image versions to 4.0.0
@@ -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}"not entirely sure why I all of a sudden needed to add these to get this to work... which I don't love
Specify user for containersto Specify user for containers and upgrade to v4.0.0tested & working. merging