質問編集履歴
1
質問の記入途中で誤って投稿してしまったため
test
CHANGED
File without changes
|
test
CHANGED
@@ -12,39 +12,117 @@
|
|
12
12
|
|
13
13
|
```
|
14
14
|
|
15
|
-
などを実行してモデルを作成しても、volumeが正しくマウントされておらず、ローカルに
|
15
|
+
などを実行してモデルを作成しても、volumeが正しくマウントされておらず、ローカルに変更が反映されていないようでした
|
16
|
+
|
17
|
+
同じような問題を解決したことがある方がいたら解決策を教えていただきたいです。
|
16
18
|
|
17
19
|
|
18
20
|
|
19
21
|
### 発生している問題・エラーメッセージ
|
20
22
|
|
23
|
+
`docker-compose up`を実行すると以下のようなメッセージが出力されます
|
24
|
+
|
21
25
|
|
22
26
|
|
23
27
|
```
|
24
28
|
|
29
|
+
Creating network "app_name_default" with the default driver
|
30
|
+
|
25
|
-
|
31
|
+
Creating app_name_db_1 ... done
|
32
|
+
|
33
|
+
Creating app_name_app_1 ... done
|
34
|
+
|
35
|
+
Attaching to app_name_db_1, app_name_app_1
|
36
|
+
|
37
|
+
db_1 | 2020-03-25T12:06:46.655110Z 0 [Note] mysqld (mysqld 5.7.10) starting as process 1 ...
|
38
|
+
|
39
|
+
db_1 | 2020-03-25T12:06:46.658851Z 0 [Note] InnoDB: PUNCH HOLE support available
|
40
|
+
|
41
|
+
db_1 | 2020-03-25T12:06:46.658899Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
42
|
+
|
43
|
+
db_1 | 2020-03-25T12:06:46.658910Z 0 [Note] InnoDB: Uses event mutexes
|
44
|
+
|
45
|
+
db_1 | 2020-03-25T12:06:46.658923Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
46
|
+
|
47
|
+
db_1 | 2020-03-25T12:06:46.658933Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
|
48
|
+
|
49
|
+
db_1 | 2020-03-25T12:06:46.658942Z 0 [Note] InnoDB: Using Linux native AIO
|
50
|
+
|
51
|
+
db_1 | 2020-03-25T12:06:46.659214Z 0 [Note] InnoDB: Number of pools: 1
|
52
|
+
|
53
|
+
db_1 | 2020-03-25T12:06:46.659388Z 0 [Note] InnoDB: Using CPU crc32 instructions
|
54
|
+
|
55
|
+
db_1 | 2020-03-25T12:06:46.669164Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
56
|
+
|
57
|
+
db_1 | 2020-03-25T12:06:46.679139Z 0 [Note] InnoDB: Completed initialization of buffer pool
|
58
|
+
|
59
|
+
db_1 | 2020-03-25T12:06:46.681668Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
|
60
|
+
|
61
|
+
db_1 | 2020-03-25T12:06:46.694269Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
|
62
|
+
|
63
|
+
db_1 | 2020-03-25T12:06:46.696008Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 11990177
|
64
|
+
|
65
|
+
db_1 | 2020-03-25T12:06:46.696050Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 11990186
|
66
|
+
|
67
|
+
db_1 | 2020-03-25T12:06:46.696429Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 11990186
|
68
|
+
|
69
|
+
db_1 | 2020-03-25T12:06:46.696473Z 0 [Note] InnoDB: Database was not shutdown normally!
|
70
|
+
|
71
|
+
db_1 | 2020-03-25T12:06:46.696490Z 0 [Note] InnoDB: Starting crash recovery.
|
72
|
+
|
73
|
+
db_1 | 2020-03-25T12:06:46.825383Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
|
74
|
+
|
75
|
+
db_1 | 2020-03-25T12:06:46.825447Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
|
76
|
+
|
77
|
+
db_1 | 2020-03-25T12:06:46.825523Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
|
78
|
+
|
79
|
+
db_1 | 2020-03-25T12:06:46.862281Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
|
80
|
+
|
81
|
+
db_1 | 2020-03-25T12:06:46.863388Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
|
82
|
+
|
83
|
+
db_1 | 2020-03-25T12:06:46.863421Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
|
84
|
+
|
85
|
+
db_1 | 2020-03-25T12:06:46.864182Z 0 [Note] InnoDB: Waiting for purge to start
|
86
|
+
|
87
|
+
db_1 | 2020-03-25T12:06:46.914477Z 0 [Note] InnoDB: 5.7.10 started; log sequence number 11990186
|
88
|
+
|
89
|
+
db_1 | 2020-03-25T12:06:46.914791Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
|
90
|
+
|
91
|
+
db_1 | 2020-03-25T12:06:46.914962Z 0 [Note] InnoDB: not started
|
92
|
+
|
93
|
+
db_1 | 2020-03-25T12:06:46.915192Z 0 [Note] Plugin 'FEDERATED' is disabled.
|
94
|
+
|
95
|
+
db_1 | 2020-03-25T12:06:46.919954Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
|
96
|
+
|
97
|
+
db_1 | 2020-03-25T12:06:46.919993Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
|
98
|
+
|
99
|
+
db_1 | 2020-03-25T12:06:46.920045Z 0 [Note] IPv6 is available.
|
100
|
+
|
101
|
+
db_1 | 2020-03-25T12:06:46.920059Z 0 [Note] - '::' resolves to '::';
|
102
|
+
|
103
|
+
db_1 | 2020-03-25T12:06:46.920068Z 0 [Note] Server socket created on IP: '::'.
|
104
|
+
|
105
|
+
db_1 | 2020-03-25T12:06:46.921117Z 0 [Note] InnoDB: Buffer pool(s) load completed at 200325 12:06:46
|
106
|
+
|
107
|
+
db_1 | 2020-03-25T12:06:46.926093Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
|
108
|
+
|
109
|
+
db_1 | 2020-03-25T12:06:46.926143Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
|
110
|
+
|
111
|
+
db_1 | 2020-03-25T12:06:46.932684Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
|
112
|
+
|
113
|
+
db_1 | 2020-03-25T12:06:46.966144Z 0 [Note] Event Scheduler: Loaded 0 events
|
114
|
+
|
115
|
+
db_1 | 2020-03-25T12:06:46.966496Z 0 [Note] mysqld: ready for connections.
|
116
|
+
|
117
|
+
db_1 | Version: '5.7.10' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)```
|
26
118
|
|
27
119
|
```
|
28
120
|
|
29
|
-
|
30
|
-
|
31
|
-
|
121
|
+
dockerについての理解がいまいちで、原因が特定できずにいます。助言をいただけると幸いです。
|
32
122
|
|
33
123
|
|
34
124
|
|
35
|
-
```ここに言語名を入力
|
36
125
|
|
37
|
-
ソースコード
|
38
|
-
|
39
|
-
```
|
40
|
-
|
41
|
-
|
42
|
-
|
43
|
-
### 試したこと
|
44
|
-
|
45
|
-
|
46
|
-
|
47
|
-
ここに問題に対して試したことを記載してください。
|
48
126
|
|
49
127
|
|
50
128
|
|
@@ -52,4 +130,4 @@
|
|
52
130
|
|
53
131
|
|
54
132
|
|
55
|
-
|
133
|
+
参考サイト:[Rails5.2(APIサーバーとして) + MySQL5.7 + Docker3メモ](https://qiita.com/gabacho/items/e8d3eb8c194d3e4b9ffa)
|