@nik202 Yeah it’s same
Once I use the other image for rasa, then there is no issue. But I can’t think of any reason why the old image is working but the new one is not.
@nik202 Why it starts new http connection on localhost:8000 instead of duckling:8000? I think that’s the problem I checked the working environment and it is making http connection on duckling:8000
I mentioned duckling:8000 url in config.yml, I don’t know what’s going on
@jpark2111 don’t copy the config.yml and endpoints…yml file to the container
COPY config.yml /app
COPY endpoints.yml /app
just check when you copy from local machine to container then just see that its copied or not.
@nik202 removed them in dockerfile, built image and run it again but it is still trying to make a connection on localhost, not on duckling. duh 
@jpark2111 can you use this command
docker run -p 8000:8000 rasa/duckling
and check ducking server is running or not?
And
train the rasa x manually
@nik202 It is listening on http://0.0.0.0:8000
Is it ok to clean up any images or layers stored in /var/lib/docker/overlay2? Would it be possible that one of those stored images are being used with wrong config(localhost:8000)?
@jpark2111 it’s taking somewhere an old config in your container, I’d recommend inspecting the container or volume or this is so strange error for me too.
@nik202 I’d like to delete images or containers that use old config, Not sure just inspecting them can resolve the issue. And how would you recommend in terms of inspecting? I tried docker inspect imageId, it just gives me an object of data
@jpark2111 hmmm, I guess you need to delete the image from the docker that’s it, and when you copy the data, first inspect the container that what you copied is what it has in it.