Docker and Network

[Phildefer]

Hi all,

I'm sorry this is maybe a stupid question but I'm a newbie.
I have a new Terra Master F4 424 Max NAS and I want to use Docker.
I can access to the TOS interface via an ip address given by my rooter (192.168.1.1) like 192.168.1.100
When I want to create a container via portainer I'd like to use the same type of addresses like 192.168.1.yyy so I try with the bridge mode but this mode has this kind of addresses : 172.17.0.xxx;
Can I create a bridge with a range like 192.168.1.2-255, how and can I give a specific address to my container like 192.168.1.200?
Thx.

[TMzethar]

Sorry, this should not be feasible. May I know why you're doing this?

[Phildefer]

Thx for your answer.

Because I managed my dockers like that on my previous Qnap NAS. It was maybe a bad habit. I'm going to change that

I need now to fix another problem : After installing a docker whatever it is I'm not able to use the console/terminal tool either on Docker Manager or on Portainer. I don`t have any error message just nothing. On Docker manager the terminal remains black with no prompt and on Portainer it remains on "connecting...". If you know why I'm interesting or I'll do another topic on the forum.

[EthanLiu]

Thx for your answer.

Because I managed my dockers like that on my previous Qnap NAS. It was maybe a bad habit. I'm going to change that

I need now to fix another problem : After installing a docker whatever it is I'm not able to use the console/terminal tool either on Docker Manager or on Portainer. I don`t have any error message just nothing. On Docker manager the terminal remains black with no prompt and on Portainer it remains on "connecting...". If you know why I'm interesting or I'll do another topic on the forum.

Please confirm whether this is the configured container and whether the configured container is available for email use. You can also try to perform related operations through the SSH backend.

[Phildefer]

The containers work ell and I use them but the console/terminal have the same problem for all containers. I dont understand this sentence : "whether the configured container is available for email use"

If it is possible I would prefer to use the GUI of Docker Manager or Portainer to access this console instead of SSH.
Thx.

[Phildefer]

I tried to do that : docker exec --interactive --tty 9c196cb9c6c6 /bin/bash

But I have this answer :
OCI runtime exec failed: exec failed: unable to start container process: open /dev/pts/1: operation not permitted: unknown

[Phildefer]

Almost solved. To use docker exec to connect to the container console you have to enabled privilege mode int the container setup.
The Docker-Manager or the Protainer console still don't work unfortunatly.

[RyanYang]

It could be that the container is not allowed inside, or that there is no container inside, or that the container is not running properly. Maybe you can try the following command:

Code: Select all

docker exec -it --interactive --tty 9c196cb9c6c6 /bin/bash

[Phildefer]

Hi TMRyan,

When I do that I have this error messqge : Error: No such container: 9c196cb9c6c6.
The only way to solve this issue is given in my previous message : Use the Privilege Mode.
It doesn't solve the console access problem with Docker-Manager or Portainer but it is possible do use a console in the terminal of TOS6.
I hope this bug is going to be fixed.
Thx.

[TMLila]

Hi TMRyan,

When I do that I have this error messqge : Error: No such container: 9c196cb9c6c6.
The only way to solve this issue is given in my previous message : Use the Privilege Mode.
It doesn't solve the console access problem with Docker-Manager or Portainer but it is possible do use a console in the terminal of TOS6.
I hope this bug is going to be fixed.
Thx.

OK, could you please tell me the image name and the specific container you deployed? Our lab will verify whether the problem you mentioned exists.