I’m almost sure you can’t (yet). The container IP’s are intended to be private, with container linking and its auto-updating of the container’s /etc/hosts file intended to cover most name based network relationships.
There are some cases where this isn’t enough though - perhaps if you can tell us more, we can help you solve your scenario.
I need stable IP for nginx configuration in web server.
Where each container is a web-site.
Thats why after container restart or docker server restart i need to config my nginx config file and every time add new IP to domain.
@jwilder has an interesting approach to this.
A containerized nginx that listens to container (re)starts and regenerates the nginx configuration accordingly. This allows to start and stop containers as you like.