[DiscordArchive] hello i have this issue ERROR: for ac-worldserver Container "042fe97562b1" is unhealthy.
[DiscordArchive] hello i have this issue ERROR: for ac-worldserver Container "042fe97562b1" is unhealthy.
Original source
hello i have this issue ERROR: for ac-worldserver Container "042fe97562b1" is unhealthy.
ERROR: for ac-authserver Container "042fe97562b1" is unhealthy.
ERROR: Encountered errors while bringing up the project. the docker logs is 2023-12-10 16:35:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.35-1.el8 started.
2023-12-10 16:35:06+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-12-10 16:35:06+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.35-1.el8 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2023-12-10T16:35:08.027773Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-12-10T16:35:08.040779Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.35) starting as process 1
2023-12-10T16:35:08.138504Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-10T16:35:29.494207Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-12-10T16:35:33.883231Z 4 [System] [MY-013381] [Server] Server upgrade from '80028' to '80035' started. Can you help me?
rektbyfaith
12-10-2023, 04:40 PM #1Archived author: laurenta78 • Posted: 2023-12-10T16:40:46.074000+00:00
Original source
hello i have this issue ERROR: for ac-worldserver Container "042fe97562b1" is unhealthy.
ERROR: for ac-authserver Container "042fe97562b1" is unhealthy.
ERROR: Encountered errors while bringing up the project. the docker logs is 2023-12-10 16:35:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.35-1.el8 started.
2023-12-10 16:35:06+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-12-10 16:35:06+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.35-1.el8 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2023-12-10T16:35:08.027773Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-12-10T16:35:08.040779Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.35) starting as process 1
2023-12-10T16:35:08.138504Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-10T16:35:29.494207Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-12-10T16:35:33.883231Z 4 [System] [MY-013381] [Server] Server upgrade from '80028' to '80035' started. Can you help me?
Original source
I checked all danglers, none of the built in docker commands work apparently the solution is either manually remove them or blow away docker completely and rebuild and restore mysql content from backup. The docker philosophy is not to worry about disk space usage.
I talk to couple other guys about it and we all came to the same conclusion. The build image and mysql image should be mounted to host to avoid the large diffs and frankly potential loss of mysql data.
rektbyfaith
12-10-2023, 04:47 PM #2Archived author: volek • Posted: 2023-12-10T16:47:52.651000+00:00
Original source
I checked all danglers, none of the built in docker commands work apparently the solution is either manually remove them or blow away docker completely and rebuild and restore mysql content from backup. The docker philosophy is not to worry about disk space usage.
I talk to couple other guys about it and we all came to the same conclusion. The build image and mysql image should be mounted to host to avoid the large diffs and frankly potential loss of mysql data.
Original source
are there any logs for ac-authserver that came out? may need to run `docker compose logs ac-authserver`
rektbyfaith
12-10-2023, 08:08 PM #3Archived author: mynameismeat • Posted: 2023-12-10T20:08:51.725000+00:00
Original source
are there any logs for ac-authserver that came out? may need to run `docker compose logs ac-authserver`
Original source
I think it's important to provide some further context to why some decisions are made. When I think about Docker for AzerothCore, I have these constraints in mind:
- the `docker-compose.yml` should be buildable
- the containers defined in `docker-compose.yml` should be "complete" - I should be able to copy only the `docker-compose.yml`, run `docker compose pull && docker compose up`, and it works. This is also to keep relative compatibility with the acore-docker repo
- the docker containers should run with acceptable performance on Windows and MacOS
- the runtime config should be relatively simple to edit through an override file
- the docker container builds should make use of build cache
MySQL defaults to a volume as the mount for the datadir as volumes have a few benefits over bind mounts, as noted in [documentation](https://docs.docker.com/storage/volumes/). Though, you raise a great point that not using a bind mount makes it easier to delete volumes, depending on the administrators' workflows (like if you run `docker compose down -v` or `docker compose down && docker system prune -fa`). In this case, it's important to note that it's recommended to use a docker-compose override file if the default compose file doesn't suit your needs. For the case of a MySQL bind mount, something like this should work
```yaml
# docker-compose.override.yml
services:
ac-database:
volumes:
# This will override the volume for docker-compose.yml. the override is based on the container path
- "./env/dist/var_lib_mysql:/var/lib/mysql"
```
For pruning the build cache, I recommend setting up [garbage collection](https://docs.docker.com/build/cache/garbage-collection), which will periodically remove build cache based on how you configure it. By default, it will prune things if build cache takes up more thean 10% of the disk, which is you have a large disk, that means a particularly large persisted cache.
rektbyfaith
12-10-2023, 08:27 PM #4Archived author: mynameismeat • Posted: 2023-12-10T20:27:05.807000+00:00
Original source
I think it's important to provide some further context to why some decisions are made. When I think about Docker for AzerothCore, I have these constraints in mind:
- the `docker-compose.yml` should be buildable
- the containers defined in `docker-compose.yml` should be "complete" - I should be able to copy only the `docker-compose.yml`, run `docker compose pull && docker compose up`, and it works. This is also to keep relative compatibility with the acore-docker repo
- the docker containers should run with acceptable performance on Windows and MacOS
- the runtime config should be relatively simple to edit through an override file
- the docker container builds should make use of build cache
MySQL defaults to a volume as the mount for the datadir as volumes have a few benefits over bind mounts, as noted in [documentation](https://docs.docker.com/storage/volumes/). Though, you raise a great point that not using a bind mount makes it easier to delete volumes, depending on the administrators' workflows (like if you run `docker compose down -v` or `docker compose down && docker system prune -fa`). In this case, it's important to note that it's recommended to use a docker-compose override file if the default compose file doesn't suit your needs. For the case of a MySQL bind mount, something like this should work
```yaml
# docker-compose.override.yml
services:
ac-database:
volumes:
# This will override the volume for docker-compose.yml. the override is based on the container path
- "./env/dist/var_lib_mysql:/var/lib/mysql"
```
For pruning the build cache, I recommend setting up [garbage collection](https://docs.docker.com/build/cache/garbage-collection), which will periodically remove build cache based on how you configure it. By default, it will prune things if build cache takes up more thean 10% of the disk, which is you have a large disk, that means a particularly large persisted cache.
1 Guest(s)
1 Guest(s)