… container definition ## Description Resolves #53 ## Why is this needed This conflict causes container creation to fail. Fixes: # ## How Has This Been Tested? I ran the setup and was able to run a workflow and deployment without issue. ## How are existing users impacted? What migration steps/scripts do we need? No impact. ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
This commit is contained in:
commit
b46a724c5a
@ -114,7 +114,6 @@ services:
|
|||||||
boots:
|
boots:
|
||||||
image: ${TINKERBELL_TINK_BOOTS_IMAGE}
|
image: ${TINKERBELL_TINK_BOOTS_IMAGE}
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
network_mode: host
|
|
||||||
command: -dhcp-addr 0.0.0.0:67 -tftp-addr $TINKERBELL_HOST_IP:69 -http-addr $TINKERBELL_HOST_IP:80 -log-level DEBUG
|
command: -dhcp-addr 0.0.0.0:67 -tftp-addr $TINKERBELL_HOST_IP:69 -http-addr $TINKERBELL_HOST_IP:80 -log-level DEBUG
|
||||||
environment:
|
environment:
|
||||||
API_AUTH_TOKEN: ${PACKET_API_AUTH_TOKEN:-ignored}
|
API_AUTH_TOKEN: ${PACKET_API_AUTH_TOKEN:-ignored}
|
||||||
|
Loading…
Reference in New Issue
Block a user