I am working on adding a Dockerfile for development/hosting of bots using this template, and I ran into an issue.
[09:23 PM] => {"type":"requestManagerFetching","data":{"method":"get","url":"https://discord.com/api/v7/gateway/bot","retryCount":0}}
[09:23 PM] => {"type":"requestManagerFetched","data":{"method":"get","url":"https://discord.com/api/v7/gateway/bot","retryCount":0,"response":{"_bodySource":{},"_stream":null,"url":"https://discord.com/api/v7/gateway/bot","statusText":"Unauthorized","status":401,"headers":{},"redirected":false,"type":"default"}}}
[09:23 PM] => {"_bodySource":{},"_stream":null,"url":"https://discord.com/api/v7/gateway/bot","statusText":"Unauthorized","status":401,"headers":{},"redirected":false,"type":"default"}
[09:23 PM] => {"type":"requestManagerFailed","data":{"method":"get","url":"https://discord.com/api/v7/gateway/bot","retryCount":0}}
I believe that this might be an API timeout or something similar, as it doesn't happen if you rerun it with the majority of the modules already cached. The issue also occurs without docker; it is just less of a problem then.
Normally this would be okay, as you just run it again, and it will finish and start the bot. The problem is that docker only saves a layer if it is successful, which this is not and it completely erases and restarts the deno cache mod.ts
layer.
I'm not sure whether this is an issue with the template or the main module, so I'll move it if this is wrong.