Skip to content
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

[docker] issue list #12

Open
2 tasks done
Alice52 opened this issue Mar 21, 2020 · 8 comments
Open
2 tasks done

[docker] issue list #12

Alice52 opened this issue Mar 21, 2020 · 8 comments
Assignees

Comments

@Alice52
Copy link
Owner

Alice52 commented Mar 21, 2020

issue1: redis

  • custom log's folder, and mounted to specify folder in the host machine:

    • this can look-up MySQL dockerFile: permission issue
    • or change config file: logfile "redis.log", then redis.log will appear in /data/
  • copy parent folder to contianer: localtion issue

    • The path must be inside the context of the build; you cannot ADD ../something/something, because the first step of a docker build is to send the context directory (and subdirectories) to the docker daemon.
    • solution2: can also use docker-compose to specify dockerfile location
@Alice52
Copy link
Owner Author

Alice52 commented Mar 21, 2020

Alice52/java-ocean#104

@Alice52 Alice52 added the help wanted Extra attention is needed label Jul 6, 2020
@Alice52
Copy link
Owner Author

Alice52 commented Jul 6, 2020

issue2: elasticsearch

  1. description

    • OK: define ENV, which can be used in runtime for startup app

    • ERROR: when I define runner.sh to startup app, and then I do create file in this shell, will get follow error log

      touch: cannot touch '/usr/share/elasticsearch/plugins/analysis-ik/config/custom.dic': Permission denied
      
  2. 这里想法是不对的, 在 compose.yml 文件中动态指定 ik 的目录是没有意义的

    • 在 build image 时配置文件已经修改了, 所以无效
    • 除非在 *.sh 内写动态修改配置文件的逻辑
  3. solution

    • consider the usage of privileged

@Alice52
Copy link
Owner Author

Alice52 commented Jul 6, 2020

issue3: network

  • compose version 3 just can be used in swarm cluster, which need three or more server: it can also run in compose.yml directly

  • but it will always failed to specify network for service, but it can be success by portainer ui.

    • this may bug of portainer

@Alice52
Copy link
Owner Author

Alice52 commented Jul 9, 2020

issue4: env, arg, docker compose env

https://vsupalov.com/docker-env-vars/

image

@Alice52 Alice52 removed the todo label Oct 25, 2020
@Alice52 Alice52 changed the title [docker file] relative docker file requirement [docker-file] relative docker file requirement Oct 25, 2020
@Alice52 Alice52 changed the title [docker-file] relative docker file requirement [docker] issue list Oct 25, 2020
@Alice52
Copy link
Owner Author

Alice52 commented Oct 25, 2020

issue 5: swarm

  • swarm
  1. use k8s instead

@Alice52
Copy link
Owner Author

Alice52 commented Oct 25, 2020

isse 6: compose version

  • [x ] upgrade docker compose version to 3.x
  1. this may bug of portainer, we can use v3 in compose.yml

@Alice52
Copy link
Owner Author

Alice52 commented Oct 26, 2020

issue7 permission

  1. es-data-permission
  2. as root using named volume

@Alice52
Copy link
Owner Author

Alice52 commented Dec 2, 2020

issue8: network[Veth Pair]

  • 分别在容器和宿主机上执行 ip link show,可查找 Veth Pair 的对应关系,再通过在宿主机上执行 brctl show,可查看该 Veth 在宿主机上对应的 bridge 名

image

@Alice52 Alice52 transferred this issue from Alice52/java-ocean Sep 11, 2023
@Alice52 Alice52 removed the help wanted Extra attention is needed label Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants