You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
overall approach: what setup do we use debug during feature development (while this is dev specific and depends on preferences some working practices would be good to know)
installation and configuration of docker/testcontainers to successfully run integration tests
installation and setup of a development database
OBS! This is a work in progress issue that I will continue to add to until I have a working code-test/debug cycle going.
Additional Setup for Testcontainer/Docker (on Linux)
For now I just dump my findings here until they take a more elaborate form.
On Linux testcontainers might fail initially with the root cause being related to "Permission denied" when trying to connect to the docker environment.
I managed to fix this by
add your user to docker user group: sudo usermod -aG docker $USER (see ^[1])
refresh the group newgrp docker
restart docker service sudo systemctl restart docker
give access to socket(?) sudo chmod 666 /var/run/docker.sock (see ^[2])
I think step 2 and 3 are only needed if you want to save you from restarting or logging out/in of your session.
Solutions were found:
The documentation so far says nothing on how to get started with development to get a code-test/debug cycle going.
So far I identified following that needs further description:
OBS! This is a work in progress issue that I will continue to add to until I have a working code-test/debug cycle going.
Additional Setup for Testcontainer/Docker (on Linux)
For now I just dump my findings here until they take a more elaborate form.
On Linux testcontainers might fail initially with the root cause being related to "Permission denied" when trying to connect to the docker environment.
I managed to fix this by
docker
user group:sudo usermod -aG docker $USER
(see ^[1])newgrp docker
sudo systemctl restart docker
sudo chmod 666 /var/run/docker.sock
(see ^[2])I think step 2 and 3 are only needed if you want to save you from restarting or logging out/in of your session.
Solutions were found:
The text was updated successfully, but these errors were encountered: