ShardingError when composing with docker?

[zSpectre0458]

ran the 'docker compose -p discord-ai up' and it keeps try to complete the shards, breaks at some point, throws an error and tries again after about 30 seconds of being dead. not sure what could be causing this, any advice or help would be grealy appreciated. the log of whats happening is below.

[Shard Manager] [INFO] Loading
bot-1 | [Shard #0] [INFO] Created shard
bot-1 | /node_modules/@discordjs/ws/dist/index.js:1151
bot-1 | error: new Error("Used disallowed intents")
bot-1 | ^
bot-1 |
bot-1 | Error: Used disallowed intents
bot-1 | at WebSocketShard.onClose (/node_modules/@discordjs/ws/dist/index.js:1151:18)
bot-1 | at connection.onclose (/node_modules/@discordjs/ws/dist/index.js:688:17)
bot-1 | at callListener (/node_modules/ws/lib/event-target.js:290:14)
bot-1 | at WebSocket.onClose (/node_modules/ws/lib/event-target.js:220:9)
bot-1 | at WebSocket.emit (node:events:518:28)
bot-1 | at WebSocket.emitClose (/node_modules/ws/lib/websocket.js:272:10)
bot-1 | at TLSSocket.socketOnClose (/node_modules/ws/lib/websocket.js:1341:15)
bot-1 | at TLSSocket.emit (node:events:530:35)
bot-1 | at node:net:343:12
bot-1 | at TCP.done (node:_tls_wrap:648:7)
bot-1 |
bot-1 | Node.js v20.18.2
bot-1 | /node_modules/discord.js/src/sharding/Shard.js:185
bot-1 | reject(new DiscordjsError(ErrorCodes.ShardingReadyDied, this.id));
bot-1 | ^
bot-1 |
bot-1 | Error [ShardingReadyDied]: Shard 0's process exited before its Client became ready.
bot-1 | at Shard.onDeath (/node_modules/discord.js/src/sharding/Shard.js:185:16)
bot-1 | at Object.onceWrapper (node:events:633:26)
bot-1 | at Shard.emit (node:events:518:28)
bot-1 | at Shard._handleExit (/node_modules/discord.js/src/sharding/Shard.js:446:10)
bot-1 | at ChildProcess.emit (node:events:518:28)
bot-1 | at ChildProcess._handle.onexit (node:internal/child_process:293:12) {
bot-1 | code: 'ShardingReadyDied'
bot-1 | }
bot-1 |
bot-1 | Node.js v20.18.2
bot-1 exited with code 1

[zSpectre0458]

so i fixed it. i dont know how but i fixed it, but i fixed it

[238SAMIxD]

Thank you for the report. Tbh it was not me who added docker so I will test it after I make an update (typescript)

[zSpectre0458]

Yeah, i dont exactly know what i did to fix it but i restarted the proccess a couple times and it just worked. i wish i could provide more info on it, there is a chance it was user error but im not technically skilled enough to be able to know