Use docker in dev?

So running the server for kobocat alone is pretty hard, do most deves just run the container? If so, are changes monitored live or do you have to restart the container after each code change? Whats best practice for getting started?

https://github.com/kobotoolbox/kobocat/issues/239 is what im hacking on now

I started each of these containers individually –

kobodocker_kobocat_1 kobodocker_mongo_1 kobodocker_rabbit_1 kobodocker_redis_main_1
kobodocker_kpi_1 kobodocker_postgres_1 kobodocker_redis_cache_1

``

and attached to cat… thats probably not the best way to go??

···

On Monday, October 16, 2017 at 7:49:26 PM UTC-6, Vincent Buscarello wrote:

So running the server for kobocat alone is pretty hard, do most deves just run the container? If so, are changes monitored live or do you have to restart the container after each code change? Whats best practice for getting started?

https://github.com/kobotoolbox/kobocat/issues/239 is what im hacking on now

The below gets this -->
2017/10/17 02:02:56 Timeout after 40s waiting on dependencies to become available: [tcp://172.17.0.2:5672]
*** /etc/my_init.d/01_wait_for_rabbit.bash failed with status 1

``

:frowning: checking rabbit
$ docker container attach kobodocker_rabbit_1
/usr/sbin/rabbitmq-server: 33: /usr/sbin/rabbitmq-server: cannot create /var/log/rabbitmq/startup_log: Permission denied

``

···

On Monday, October 16, 2017 at 8:02:30 PM UTC-6, Vincent Buscarello wrote:

I started each of these containers individually –

kobodocker_kobocat_1 kobodocker_mongo_1 kobodocker_rabbit_1 kobodocker_redis_main_1
kobodocker_kpi_1 kobodocker_postgres_1 kobodocker_redis_cache_1

``

and attached to cat… thats probably not the best way to go??

On Monday, October 16, 2017 at 7:49:26 PM UTC-6, Vincent Buscarello wrote:

So running the server for kobocat alone is pretty hard, do most deves just run the container? If so, are changes monitored live or do you have to restart the container after each code change? Whats best practice for getting started?

https://github.com/kobotoolbox/kobocat/issues/239 is what im hacking on now

trying to use kobo-docker I get
ImportError: No module named django_digest
ERROR: Service ‘kpi’ failed to build: The command ‘/bin/sh -c python manage.py collectstatic --noinput’ returned a non-zero code: 1

``

from docker-compose

···

On Monday, October 16, 2017 at 8:05:26 PM UTC-6, Vincent Buscarello wrote:

The below gets this -->
2017/10/17 02:02:56 Timeout after 40s waiting on dependencies to become available: [tcp://172.17.0.2:5672]
*** /etc/my_init.d/01_wait_for_rabbit.bash failed with status 1

``

:frowning: checking rabbit
$ docker container attach kobodocker_rabbit_1
/usr/sbin/rabbitmq-server: 33: /usr/sbin/rabbitmq-server: cannot create /var/log/rabbitmq/startup_log: Permission denied

``

On Monday, October 16, 2017 at 8:02:30 PM UTC-6, Vincent Buscarello wrote:

I started each of these containers individually –

kobodocker_kobocat_1 kobodocker_mongo_1 kobodocker_rabbit_1 kobodocker_redis_main_1
kobodocker_kpi_1 kobodocker_postgres_1 kobodocker_redis_cache_1

``

and attached to cat… thats probably not the best way to go??

On Monday, October 16, 2017 at 7:49:26 PM UTC-6, Vincent Buscarello wrote:

So running the server for kobocat alone is pretty hard, do most deves just run the container? If so, are changes monitored live or do you have to restart the container after each code change? Whats best practice for getting started?

https://github.com/kobotoolbox/kobocat/issues/239 is what im hacking on now