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-compose lost prefix in logging. #63

Closed
weihao opened this issue May 30, 2021 · 4 comments
Closed

Docker-compose lost prefix in logging. #63

weihao opened this issue May 30, 2021 · 4 comments

Comments

@weihao
Copy link
Contributor

weihao commented May 30, 2021

bungeecord1    | WARNING: An illegal reflective access operation has occurred
bungeecord1    | WARNING: Illegal reflective access by us.myles.ViaVersion.bungee.platform.BungeeViaInjector (file:/server/plugins/ViaVersion-3.2.2-SNAPSHOT.jar) to field java.lang.reflect.Field.modifiers
bungeecord1    | WARNING: Please consider reporting this to the maintainers of us.myles.ViaVersion.bungee.platform.BungeeViaInjector
bungeecord1    | WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
bungeecord1    | WARNING: All illegal access operations will be denied in a future release
survival_1     | [00:51:09 INFO]:         __
survival_1     | [00:51:09 INFO]:   |    |__)   LuckPerms v5.3.3
survival_1     | [00:51:09 INFO]:   |___ |      Running on Bukkit - Paper
survival_1     | [00:51:09 INFO]:
survival_1     | [00:51:09 INFO]: [LuckPerms] Loading configuration...
lobby2_1       | [00:51:09 INFO]: [LuckPerms] Loading storage provider... [MYSQL]
00:51:09 [INFO] [ViaVersion] Loading 1.16 -> 1.16.2 mappings...
00:51:09 [INFO] [ViaVersion] ViaVersion detected server version: 1.8.x (47)
00:51:09 [INFO] Enabled plugin ViaVersion version 3.2.2-SNAPSHOT by _MylesC, creeper123123321, Gerrygames, KennyTV, Matsv
00:51:09 [INFO] Enabled plugin cmd_server version git:cmd_server:1.16-R0.5-SNAPSHOT:d49e97c:1575 by SpigotMC
00:51:09 [INFO] Enabled plugin cmd_alert version git:cmd_alert:1.16-R0.5-SNAPSHOT:d49e97c:1575 by SpigotMC
00:51:09 [INFO] Enabled plugin cmd_send version git:cmd_send:1.16-R0.5-SNAPSHOT:d49e97c:1575 by SpigotMC
lobby1_1       | [00:51:09 INFO]: [FancyCropTrample] Loading FancyCropTrample v1.2.2
lobby1_1       | [00:51:09 INFO]: [VoidGenerator] Loading VoidGenerator v1.7.0
lobby1_1       | [00:51:09 INFO]: Server permissions file permissions.yml is empty, ignoring it
lobby1_1       | [00:51:09 INFO]: [LuckPerms] Enabling LuckPerms v5.3.3
lobby2_1       | [00:51:09 INFO]: [me.lucko.luckperms.lib.hikari.HikariDataSource] luckperms-hikari - Starting...
lobby2_1       | [00:51:09 INFO]: [me.lucko.luckperms.lib.hikari.HikariDataSource] luckperms-hikari - Start completed.
00:51:10 [INFO] [ServerManager] Couldn't check for an update
00:51:10 [INFO] [ServerManager] You're on the latest version!
00:51:10 [INFO] [ViaVersion] Finished mapping loading, shutting down loader executor!
00:51:10 [INFO] [ServerManager] Couldn't check for an update
00:51:10 [INFO] [ServerManager] You're on the latest version!

As you can see, when running bungee docker image as service, it is not prepending container names to the logs.

  bungeecord1: # does not label the logs
    image: itzg/bungeecord
    container_name: "bungeecord1" # does not label the logs
    ports:
      - "25566:25565"
      # - "19132:19132/udp"
    volumes:
      - "./bungeecord/plugins:/plugins/:ro" # <-
      - "./bungeecord/config:/config/:ro"
    environment: 
      MEMORY: "4096m"
    restart: always
    depends_on:
      - "redis"
      - "db"
@itzg
Copy link
Owner

itzg commented May 30, 2021

I see what you mean, but I'm not sure if there's anything I can do via the image itself.

@weihao
Copy link
Contributor Author

weihao commented May 30, 2021

Let's do more research why bungee container is behaving like this.

@weihao
Copy link
Contributor Author

weihao commented Jun 13, 2021

Fixed

@weihao weihao closed this as completed Jun 13, 2021
@SQReder
Copy link

SQReder commented Jul 11, 2021

@weihao I'm running into it again. What fix you applied?
image

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