Here&#39;s the mighty eagle that docker has recently included. :D

You can [`update`](https://docs.docker.com/engine/reference/commandline/update/) docker container.

use **`sudo docker update --restart=no &lt;container_id&gt;`** to update `--restart` flag of the container.

Now you can [`stop`](https://docs.docker.com/engine/reference/commandline/stop/) the container.

You should be able to just use docker stop and then docker rm to make sure the container doesn&#39;t restart when the daemon restarts. 

Your question is an issue on the docker [github][1] and someone has made some comments about to how to solve [here][2]

&gt; I&#39;m not sure if it&#39;s intended behavior to restart a stopped container on daemon restart... but for sure docker rm &lt;container&gt; would be all that is needed, no need to remove the image.

  [1]: https://github.com/docker/docker/issues/11008
  [2]: https://github.com/docker/docker/issues/10032

If you use docker stop or docker kill, you&#39;re manually stopping the container so it will not restart. You can do some tests about restart policies: restarting the docker daemon, rebooting your server, using a CMD inside a container and running an exit...

See this answer for more details:

https://serverfault.com/a/884823/381420

I&#39;m making a website with React, React Router, and Redux. Lots of routes (pages) require users to be logged in. I can redirect to the login page if the user is not logged in like this:

	function requireAuth(nextState, replace) {
		let loggedIn = store.getState().AppReducer.UserReducer.loggedIn;

		if(!loggedIn) {
			replace({
				pathname: &#39;/login&#39;,
				state: {
					nextpathname: nextState.location.pathname
				}
			});
		}
	}

	ReactDOM.render(
		&lt;Provider store={store}&gt;
			&lt;Router history={history}&gt;
				&lt;Route path=&quot;/&quot; component={App}&gt;
					&lt;IndexRoute component={Index} /&gt;
					&lt;Route path=&quot;login&quot; component={Login} /&gt;
					&lt;Route path=&quot;register&quot; component={Register} /&gt;
					&lt;Route path=&quot;dashboard&quot; component={Graph} onEnter={requireAuth}&gt;
						... some other route requires logged in ...
					&lt;/Route&gt;
				&lt;/Route&gt;
			&lt;/Router&gt;
		&lt;/Provider&gt;,
		document.getElementById(&#39;entry&#39;)
	);

Please see the code, I used the onEnter hook to redirect to the &#39;/login&#39; route if the user is not logged in. Data for checking if the user is logged in is in the store and it will update after the user logs in.

It&#39;s working perfectly, but the problem is when I refresh the page, the store is reset and the user is not logged in state back.

I know this happens because the Redux store is just memory storage, so refreshing the page will lose all data from the store.

Checking the server session on every refresh may work but this might be too many requests, so that seems like a bad idea.

Saving the logged in state data to localStorage might work, but in this case, I should check every AJAX calls fail that request rejected because session is expired or not exists like something, and that seems like a bad idea too.

Is there a way to solve this problem more simply? My website needs to handle lots of users so I want to reduce XHR calls as much as possible.

Any advice will be very appreciated.

On React Router, how to stay logged in state even page refresh?

Is `json.loads` from Python&#39;s standard `json` module vulnerable to arbitrary code execution or any other security problems?

My application can receive JSON messages from non-trustworthy sources.

Is json.loads() vulnerable to arbitrary code execution?

Is there any way to stop a docker container which started with **`--restart=always`** like following

`sudo docker run -it --restart=always &lt;image_id&gt;` 

How to stop a docker container which started with `--restart=always`

Is there any way to stop a docker container which started with <code>--restart=always</code> like following
<code>sudo docker run -it --restart=always &#x3C;image_id></code>

`compose.yml` file, which looks like this:

    version: &#39;2&#39;
    services:
      discovery-microservice:
        build: discovery-microservice
          context: /discovery-microservice/target/docker
          dockerfile: Dockerfile
      ports:
       - &quot;8761:8761&quot;

While I am executing it I get the following error:
     
    yaml.scanner.ScannerError: mapping values are not allowed here
    in &quot;C:\...\docker-compose.yml&quot;, line 5, column 14

From what I see, nothing is wrong with the format, e.g. whitespaces missing. My overall goal is to specify a development mode docker-compose file, pointing it to the target directories from the different modules.    
What am I doing wrong here?

Docker-Compose file has yaml.scanner.ScannerError

I&#39;ve noticed that many entrypoint.sh scripts for docker do something like this:

    #!/bin/bash
    set -e
    
    ... code ...
    
    exec &quot;$@&quot;

What are the `set -e` and the `exec &quot;$@&quot;` for?


What does set -e and exec &quot;$@&quot; do for docker entrypoint scripts?

Using ubuntu tusty, there is a service running on a remote machine, that I can access via port forwarding through an ssh tunnel from `localhost:9999`.

I have a docker container running. I need to access that remote service via the host&#39;s tunnel, from within the container.


I tried tunneling from the container to the host with `-L 9000:host-ip:9999` , then accessing the service through `127.0.0.1:9000` from within the container fails to connect. To check wether the port mapping was on, I tried
```
nc -luv -p 9999 # at host
nc -luv -p 9000 # at container
```

following [this, parag. 2][1] but there was no perceived communication, even when doing 
```
nc -luv host-ip -p 9000 
```  at the container

I also tried mapping the ports via `docker run -p 9999:9000 ` , but this reports that the bind failed because the host port is already in use (from the host tunnel to the remote machine, presumably).

So my questions are

1 - How will I achieve the connection?  Do I need to setup an ssh tunnel to the host, or can this be achieved with the docker port mapping alone?

2 - What&#39;s a quick way to test that the connection is up? Via bash, preferably.

Thanks.
  [1]: http://www.binarytides.com/netcat-tutorial-for-beginners/

access host&#39;s ssh tunnel from docker container

**Problem**

It seems `systemd` is not active or available in Ubuntu Docker containers. 

**Setup**

I&#39;m running Docker containers from the `ubuntu:16.04` and `ubuntu:16.10` images.

**Tests**

If I execute:

`systemctl status ssh` in the `16,04` container

the result is the error `Failed to connect to bus: No such file or directory`

In the `16.10` container the error is: `bash: systemctl: command not found`.

If I do `which systemctl` systemctl is found in the `16.04` container but not in the `16.10` container.

I have spotted that `/lib/systemd` exists. 

I have tried installing systemd with:

`apt-get install systemd libpam-systemd systemd-ui`

Then `which systemctl` finds systemctl in `16.10`

but `systemctl status ssh` still gives the error `Failed to connect to bus: No such file or directory`

**Questions**

How can systemd and systemctl be activated for use in Ubuntu Docker images?

Why is systemd not active in Ubuntu Docker containers? Is systemd not used in instantiating the container?

I have failed to find any documentation on this topic for Ubuntu / Ubuntu Docker images, only information on the Ubuntu transition from `Upstart` to `systemd`. Is there any documentation giving a full explanation?

Not able to use systemd on ubuntu docker container

I can&#39;t seem to get MySQL data to persist if I run `$ docker-compose down` with the following `.yml`

    version: &#39;2&#39;
    services:
      # other services

      data:
        container_name: flask_data
        image: mysql:latest
        volumes:
          - /var/lib/mysql
        command: &quot;true&quot;

      mysql:
        container_name: flask_mysql
        restart: always
        image: mysql:latest
        environment:
          MYSQL_ROOT_PASSWORD: &#39;test_pass&#39; # TODO: Change this
          MYSQL_USER: &#39;test&#39;
          MYSQL_PASS: &#39;pass&#39;
        volumes_from:
          - data
        ports:
          - &quot;3306:3306&quot;
    

My understanding is that in my `data` container using `volumes: - /var/lib/mysql` maps it to my local machines directory where mysql stores data to the container and because of this mapping the data should persist even if the containers are destroyed. And the `mysql` container is just a client interface into the db and can see the local directory because of `volumes_from: - data`

Attempted this answer and it did not work. https://stackoverflow.com/questions/34511336/docker-compose-persistent-data-trouble

**EDIT**

Changed my `.yml` as shown below and created a the dir `./data` but now when I run `docker-compose up --build` the `mysql` container wont start throws error saying

      data:
        container_name: flask_data
        image: mysql:latest
        volumes:
          - ./data:/var/lib/mysql
        command: &quot;true&quot;

      mysql:
        container_name: flask_mysql
        restart: always
        image: mysql:latest
        environment:
          MYSQL_ROOT_PASSWORD: &#39;test_pass&#39; # TODO: Change this
          MYSQL_USER: &#39;test&#39;
          MYSQL_PASS: &#39;pass&#39;
        volumes_from:
          - data
        ports:
          - &quot;3306:3306&quot;


    flask_mysql | mysqld: Can&#39;t create/write to file &#39;/var/lib/mysql/is_writable&#39; (Errcode: 13 - Permission denied)
    flask_mysql | 2016-08-26T22:29:21.182144Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    flask_mysql | 2016-08-26T22:29:21.185392Z 0 [ERROR] --initialize specified but the data directory exists and is not writable. Aborting.

Content Type	Original Author	Original Content on Stackoverflow
Question	Rafaf Tahsin	View Question on Stackoverflow
Solution 1 - Docker	Rafaf Tahsin	View Answer on Stackoverflow
Solution 2 - Docker	zhqiat	View Answer on Stackoverflow
Solution 3 - Docker	Achraf JEDAY	View Answer on Stackoverflow

How to stop a docker container which started with `--restart=always`

Docker Problem Overview

Docker Solutions

Solution 1 - Docker

Solution 2 - Docker

Solution 3 - Docker

Is json.loads() vulnerable to arbitrary code execution?

On React Router, how to stay logged in state even page refresh?

Attributions