-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate best practices for creating an XLoader Docker image + subsequent CKAN (worker) container #66
Comments
I have a background worker running in it’s own container however I have the following problem: Replacement of DataPusher with XLoader: CKAN (UI) runs in it’s own image/container These 2 containers are on the same Docker network
In the past I have had to configure XLoader (worker) in the UI container as I couldn’t get it running in a separate container. My questions re: Are any of these variables used for XLoader? I assume not… To get the background worker getting “triggered” to Express Load a dataset resource into the Datastore I have had to include the xloader plugin in the CKAN UI container as well as the CKAN worker container. However only the worker container runs “ I have tried this setup in both Production mode and Development mode. I get the following error in Dev mode I get a similar error in Production mode. It seems XLoader uses the To workaround this I had to add an entry into the Here is the log from a successful xloader load: I must be missing something here…any idea? |
Update 1: I have tried updating both the |
Update 2: I have managed to get it working but it's not a great solution. Docker containers can access the host network using the If I also add an entry to my Mac OS hosts file for |
Eventually XLoader will replace DataPusher as the de facto tool to load tabular data into the CKAN DataStore.
Ideally, XLoader will be running in it's own container so will need CKAN installed also
The "worker" process is
ckan -c /etc/ckan/default/ckan.ini jobs worker
Is there a better way to wrap this process to take advantage of native Docker methods to do this?Will we use supervisor to look after the running worker process?
ckanext.xloader.api_token
is also required to be set somewhere within the setup scriptsThe text was updated successfully, but these errors were encountered: